I’ve been the (un)lucky one that hit the issue where a number of my test VMs all fail to upgrade from build 10159 to 10162. Despite trying all those integrity scans (chkdsk c: /f /r /x) or cleanups (Disk cleanups with remove previous builds) it always failed at around 40%. This was happening on multiple machines (VMs) – some on VirtualBox and even one on Hyper-V.
Checking the setuperr.log file it always seemed the following line was the culprit:
Error [0x018046] CSI 0000013b (F) Failed execution of queue item Installer: ServiceModelReg Installer ({79675b3f-2054-4efd-aa9d-e1830916be47}) with HRESULT HRESULT_FROM_WIN32(52). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
Unfortunately the Internet (Google and Bing) wasn’t kind finding any help on this. Then out of desperation I looked at some of the ‘earlier’ errors which seemed to be ignored and that is all related tp IIS App pool (since I have IIS and Visual Studio 2015 RC installed). I even tried uninstalling Visual Studio on one instance but still no luck. In a moment of almost pure madness I launched the ‘Windows Features’ from Control panel and simply removed IIS from the current installation (including HTTP Activation from the .Net installs). It does not make sense that Microsoft would break their upgrade process due to one of their own technologies but there you have it!
Rerun the upgrade again and… whola it works.
Update: I’ve now confirmed this on 3 different machines. 2 VirtualBox VMs and one Hyper-V VM.
Update 2: Seems the problem is more about having both .Net 3.x and 4.x HttpActivation features on at the same time – http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/bug-upgrade-81-to-windows-build-10162-fails-if/228b1433-823e-4cd4-90da-72be01c592fb?auth=1
0 Comments.