Jump to content

Recommended Posts

Try this ?

Repair the .Net framework 4.0 in Control Panel:

Click Start > Control Panel > Programs and Features, select Microsoft .NET Framework 4 Client Profile, and click Uninstall/Change.

In the Maintenance screen that opens, choose "Repair .NET Framework 4 Client Project to its original state" and click Next.

After the repair completes, click Finish.

When you return to Windows Update, the .NET patches should install without a hitch.

Link to comment
Share on other sites

Tried this, and it took about 5 minutes. Went to update and not even 5 minutes after the update it's asking to update again. Anything else i can do?

Try this ?

Repair the .Net framework 4.0 in Control Panel:

Click Start > Control Panel > Programs and Features, select Microsoft .NET Framework 4 Client Profile, and click Uninstall/Change.

In the Maintenance screen that opens, choose "Repair .NET Framework 4 Client Project to its original state" and click Next.
After the repair completes, click Finish.
When you return to Windows Update, the .NET patches should install without a hitch.

Link to comment
Share on other sites

  • 4 weeks later...

It looks like the updates are successfully installed each time. That has been known to happen with some Microsoft updates in the past. I will have a more detailed look into this when I have a little spare time later today or tomorrow.

Anything yet? Still the same, asking to be updated right after i update.

Link to comment
Share on other sites

Maybe this will help:


http://support.microsoft.com/kb/2431208






SYMPTOMS
An update for the Microsoft .NET Framework version 4 may not install if the following conditions are true:
  • You previously installed the Microsoft .NET Framework 4 or the Microsoft .NET Framework 4 Client Profile.

  • A system restart is pending but has not been completed before you install the new update.

Note If you install the update by using the Windows Update site, it may seem that the update was offered and installed. However, after you restart the computer, the same update is offered again.



CAUSE
This issue occurs because, when the Microsoft .NET Framework 4 is installed, certain components are locked or are being used until the system is restarted. These components cannot be updated until the system is restarted. Because of this, in the scenario described in the Symptoms section, the version of the shim (mscoree.dll) is the Microsoft .NET Framework version 3.5 SP1 or earlier. The installation of the Microsoft .NET Framework 4 deploys certain settings which prevent the older shim from working correctly until the shim is updated after the system is restarted. In this scenario, if you try to install another update for the Microsoft .NET Framework while the restart is pending, the update will try to use a Global Assembly Cache (GAC) deployment for the files in the update. This GAC operation requires the shim. However, because the shim is in an inconsistent state pending a restart, the GAC operation will fail. This causes the update to fail.



WORKAROUND
To avoid this issue, restart the system before you install the new Microsoft .NET Framework updates. If you have already experienced the condition, and an update did not install because of this issue, restart the computer and then reinstall the new updates.


Link to comment
Share on other sites

Maybe this will help:

http://support.microsoft.com/kb/2431208

SYMPTOMS

An update for the Microsoft .NET Framework version 4 may not install if the following conditions are true:

  • You previously installed the Microsoft .NET Framework 4 or the Microsoft .NET Framework 4 Client Profile.
  • A system restart is pending but has not been completed before you install the new update.
Note If you install the update by using the Windows Update site, it may seem that the update was offered and installed. However, after you restart the computer, the same update is offered again.

CAUSE

This issue occurs because, when the Microsoft .NET Framework 4 is installed, certain components are locked or are being used until the system is restarted. These components cannot be updated until the system is restarted. Because of this, in the scenario described in the Symptoms section, the version of the shim (mscoree.dll) is the Microsoft .NET Framework version 3.5 SP1 or earlier. The installation of the Microsoft .NET Framework 4 deploys certain settings which prevent the older shim from working correctly until the shim is updated after the system is restarted. In this scenario, if you try to install another update for the Microsoft .NET Framework while the restart is pending, the update will try to use a Global Assembly Cache (GAC) deployment for the files in the update. This GAC operation requires the shim. However, because the shim is in an inconsistent state pending a restart, the GAC operation will fail. This causes the update to fail.

WORKAROUND

To avoid this issue, restart the system before you install the new Microsoft .NET Framework updates. If you have already experienced the condition, and an update did not install because of this issue, restart the computer and then reinstall the new updates.

I've always restarted or even shutdown and it updates ALWAYS, when i turn on or log on it automatically asks to be updated again. I don't know what to do

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy