M Martin2 Member Joined Aug 28, 2016 Posts 12 Sep 9, 2016 #21 Problem solved! I now managed to successfully install the Anniversary Update. The image path in the WIMMount registry key was wrong: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount The key "ImagePath" was set different than to "system32\drivers\wimmount.sys". This was because I installed a program that created an emergency DVD with Windows 10 from a German computer magazine. I found the issue (not to be able to mount the WIM file) in the log files where you provided the path to. Thanks for this, I didn't know of the existance of these files before. I then googled this issue and found a German page where they pointed to that issue: Windows 10 Update abgebrochen - Failed to mount WIM file - SteebIT Therefore I changed the path in the registry, rebooted, installed Windows 10 AU and this time - no error. Perfect. Thank you so much for your help!
Problem solved! I now managed to successfully install the Anniversary Update. The image path in the WIMMount registry key was wrong: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount The key "ImagePath" was set different than to "system32\drivers\wimmount.sys". This was because I installed a program that created an emergency DVD with Windows 10 from a German computer magazine. I found the issue (not to be able to mount the WIM file) in the log files where you provided the path to. Thanks for this, I didn't know of the existance of these files before. I then googled this issue and found a German page where they pointed to that issue: Windows 10 Update abgebrochen - Failed to mount WIM file - SteebIT Therefore I changed the path in the registry, rebooted, installed Windows 10 AU and this time - no error. Perfect. Thank you so much for your help!
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Sep 9, 2016 #22 I saw from your logs that it was a mounting error. I was JUST about to start researching about it Glad to see that it worked for you, thank you for letting us know what the solution was, it's always helpful! And no problem, you're welcome!
I saw from your logs that it was a mounting error. I was JUST about to start researching about it Glad to see that it worked for you, thank you for letting us know what the solution was, it's always helpful! And no problem, you're welcome!