Computer caught in UPDATES LOOP

R

Richard

Earlier I tried to install fee trial NERO 10 from WWW. Did not intall
and I think it was a .NET issue. Tried then to install NERO 9 Lite, that
failed to install.

Anyway, on boot-up I notice that Automatiic Updates wants to install 3
updates KB979909; KB974417; KB982168.

These initialise and install. But sometime on turn off, PC wanted to
install them again as it's turning off.

Anyway, last time I unstall updates the PC turned off immediately.

I thought great, but, when I boot up Automatic Installer shows same 3
updtaes to install.

A loop situation here. How can I stop it? TIA.
 
R

Richard

See my post in this thread, Richard:
http://social.answers.microsoft.com/Forums/en/vistawu/thread/5dc22ff1-ba9a-4a3a-9f19-49e85908c4c9


Please note that KB982168 is an Optional, non-security update; feel free
to "hide" it.

There is a corruption in .NET I think. This is why NERO would not
install. NERO told me what it was that did not succeed .NET 3.5,
-something like that.

This thread is somewhere near, I might find something here:

http://forums.cnet.com/5208-6142_102-0.html?threadID=397538&tag=forum-w;forums06
 
R

Richard

There is a corruption in .NET I think. This is why NERO would not
install. NERO told me what it was that did not succeed .NET 3.5,
-something like that.

This thread is somewhere near, I might find something here:

http://forums.cnet.com/5208-6142_102-0.html?threadID=397538&tag=forum-w;forums06

I fixed it.

Basically I removed all .NET with:

http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

and then reinstalled .NET 3.5.

and got all the current updates.
 
P

PA Bear [MS MVP]

Richard said:
There is a corruption in .NET I think. This is why NERO would not
install. NERO told me what it was that did not succeed .NET 3.5,
-something like that.
<SNIP>
Many third-party apps (including heavy hitters like Intuit QuickBooks &
Oracle) haven't been updated in ages (or people are using outdated versions)
and therefore weren't compatible with the changes introduced in these recent
..NET Framework updates, especially the security-related updates.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top