• Feature update to Windows 10, version 1607. Problems

DavidY said:

Yes - you'll need to copy it to another folder and look at it there. You'll need to provide admin permission, but it should allow you to copy the file.

Here is the file.

David49 said:

Here is the file.

I can't see any errors in there, I must admit.

David49 said:

Do you think I could try to run the update again?

Yes I guess so.

Once again failure occurred at 40% with the same error code when booting into my restored version of Windows. If my current version of Windows is happy with my system, I wonder why this update isn't?

David49 said:

Once again failure occurred at 40% with the same error code when booting into my restored version of Windows. If my current version of Windows is happy with my system, I wonder why this update isn't?

My only suggestion is to try the remedy at the end of that MSDN blog post, which is to delete 3 specific keys from the folder: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. To be safe I'd take copies first and store them in another folder before deleting.

The solution:

The RSA machine keys in Windows 7 and Windows 2008 are found at the following location:

C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys

The ACLs (access control lists) for the IIS keys are incorrect, hence the failure. The keys in question are the following (files starting with the numbers indicated and ending in the machine’s GUID):

6de9cb26d2b98c01ec4e9e8b34824aa2_GUID iisConfigurationKey
d6d986f09a1ee04e24c949879fdb506c_GUID NetFrameworkConfigurationKey
76944fb33636aeddb9590521c2e8815a_GUID iisWasKey

The easiest solution is to remove the files from the folder, as new ones will be re-created the next time you try and install IIS. This allows the IIS installation to succeed, and hence, it allows the upgrade to complete successfully.

There may be more files in the folder, but I think it's these specific ones you want.
Then try the installation again, I guess.

It's past bedtime in this timezone so logging off now...

DavidY said:

My only suggestion is to try the remedy at the end of that MSDN blog post, which is to delete 3 specific keys from the folder: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. To be safe I'd take copies first and store them in another folder before deleting.

There may be more files in the folder, but I think it's these specific ones you want.
Then try the installation again, I guess.

It's past bedtime in this timezone so logging off now...

Thanks. I will try your suggestion. BTW, there are 280 lines in that folder. All of them hexidecimal at least twice as long as those 3 files I'm supposed to delete, with no words in them.

Failure happened exactly as all the times before.

I believe that there is still some issue with IIS, or some file related to its configuration.

When Windows tries to upgrade to the next version, it tries to migrate IIS from the old windows version to the new one, and it trips over that issue, causing the installation to fail.

Some more things to try:

• Make sure you have a good backup
• Switch off those two Internet Information Services features in the same place as you switched them on before. I'm assuming here that you don't need IIS to run some sort of internet feature?
• You may have already done this but if not, run the SFC (system file checker) command - see here: SFC Command - Run in Windows 10
• Depending what that says, you might want to use DISM to repair the Windows 10 image - DISM - Repair Windows 10 Image
• Restart the computer
• Try again from the 1607 ISO route suggested earlier.

I ran the SFC scan and got this result:


I am running the restore health cmd now.

I wish I could attach the log file. But it is showing 38KB in the Documents folder, and 38MB on the desktop. I cannot bring it in here from either location.

I would love to attach the log file, but it is 2.38MB and this forum has a limit of 2.00MB