For a couple of weeks now, my Surface Pro 3 has been trying to install the Windows 10 Anniversary Edition which comes through Windows Update. Each time, it fails and rolls back to the earlier O/S.
After some digging, I found the following error in c:/$$WINDOWS.~BT/Sources/Rollback/setupapi/setupapi.offline.log:
!!! flq: Error installing file (0x00000002)
!!! flq: Error 2: The system cannot find the file specified.
! flq: SourceFile - 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_x86_f375652b13ce5766\Amd64\UNIRES.DLL'
! flq: TargetFile - 'C:\$WINDOWS.~BT\NewOS\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_f375652b13ce5766\Amd64\UNIRES.DLL'
!!! cpy: Failed to copy file 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_x86_f375652b13ce5766\Amd64\UNIRES.DLL' to 'C:\$WINDOWS.~BT\NewOS\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_f375652b13ce5766\Amd64\UNIRES.DLL'. Error
= 0x00000002
[snip]
<<< [Exit status: FAILURE(0x00000002)]
It appears drivers for Surface Pro3 are installed with Architecture = amd64 (I'm not sure why, since my Surface Pro has an i7 processor), but the above is trying to find the AMD64 driver inside of the ntprint.inf_x86_... directory ... and
failing, because of course that directory only contains an x86 driver, not amd64.
Looking at SetupPlatform.Drivers.inf, I see that every single driver has a filename whatever.inf_amd64_... except the ntprint.inf driver which is x86. This is the only driver out of a list of 210 drivers that is x86 instead of amd64. Here's an excerpt from SetupPlatform.Drivers (I added boldface):
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\rtsu82.inf_amd64_aa0ce2d8f9796789\rtsu82.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\samfirmware.inf_amd64_35d5bbd1cf528b7b\samfirmware.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\ialpss_spi.inf_amd64_4617314fce292e85\ialpss_spi.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\vlv2smb.inf_amd64_f3783da915bfc703\vlv2smb.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\ntprint.inf_x86_f375652b13ce5766\ntprint.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\lxptusb3.inf_amd64_b4af0c5894951f4c\lxptusb3.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\patusb.inf_amd64_7b3ce456e8bfcaa7\patusb.inf
0|GlobalPath,{3C7DD483-6AA9-4AB6-8DDE-F7CE732275F4},0,711983104,4228855084,Windows\System32\DriverStore\FileRepository\surfacetouchcoverfwupdate.inf_amd64_0e9feb136f2304a5\surfacetouchcoverfwupdate.inf
So this suggests to me that the build being distributed for Surface Pro 3 has an error, namely that the wrong flavor of the ntprint driver is supplied, leading to an install failure that causes the upgrade to roll back.
Is there a MS O/S expert reading this who can confirm this is the problem, and hopefully fix the build that is being distributed through WU? It is highly annoying that every few days my computer tries to upgrade to the new O/S build and fails.
Thanks!