Windows 10: • Feature update to Windows 10, version 1607. Problems

What antivirus software you are using? Sometimes the AV application is preventing the upgrade, especially third party programs like Avast.

My next try would be to first disable / turn off both AV and Firewall, then run setup again.

 

I'm using 360 Total Security and GlassWire Network Security

But these shouldn't affect anything after the first reboot, would they?

 

Yes, they might affect. Your upgrade is failing during the sysprep, which is when Windows setup goes through and checks the system for existing components and settings.

As I said, I would turn both AV and Firewall off and run setup again. Turn them off and restart, check after restart that both really are off, then run setup.

If upgrade still fails we have to think something else, but this would be my first choice.

 

Ok, I will try that.

 

Ok, I will try that. It could also be a good idea to disconnect your external HDD and USB while you run Setup.

 

I will try that next. With my anti-virus and firewall uninstalled, and Win Defender disabled, update failed with the same error message. Why does it have to be this difficult? Thanks to everyone for trying to help me. I will let you know how my next attempt works out.

 

BTW, my keyboard and mouse are wireless USB. should they be ok to keep during the update?

 

You'll have to keep the keyboard (unless you have another keyboard you could plug in directly). Try with the bare minimum of USB devices attached. Once installed, they can all be plugged in again. The less there is for Setup to configure, the better the chance of success.

 

Even if I had a wired keyboard and mouse, they would have to be connected to USB ports anyway.

Ok, tried that and update failure occurred at 40% as usual with the same error codes. I don't know what is left to try. Anyone?

 

I still think it's worth looking for the log files setupact.log (and perhaps setuperr.log) to see if they say anything useful about what went wrong.

 

I have both of those files. setuperr.log is an empty text tile. I will try to attach the setupact.log file here.

2017-02-17 12:09:20, Info UI Determining whether we should run ConX or legacy setup
2017-02-17 12:09:20, Info UI Will launch ConX setup experience
2017-02-17 12:09:20, Info UI Launching ConX setup experience
2017-02-17 12:09:20, Info UI Inspecting ConX Setup Cmdline
2017-02-17 12:09:20, Info UI Launching H:\Sources\SetupPrep.exe
2017-02-17 12:16:33, Info MIG MigHost started with command line: {837B264C-106F-4371-A9AF-2EE07C7C63B8} /InitDoneEvent:MigHost.{837B264C-106F-4371-A9AF-2EE07C7C63B8}.Event /ParentPID:12144
2017-02-17 12:16:33, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.
2017-02-17 12:16:33, Info MIG MigHost: Initialized successfully with CLSID[{837B264C-106F-4371-A9AF-2EE07C7C63B8}] and LogDir=[]
2017-02-17 12:16:33, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer in progress: BinaryPath=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0].
2017-02-17 12:16:33, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x4730], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]
2017-02-17 12:16:33, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2017-02-17 12:16:34, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2017-02-17 12:16:34, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.
2017-02-17 12:16:34, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].
2017-02-17 12:16:34, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x4730].
2017-02-17 12:16:34, Info MIG MigHost: Exiting process.

 

Where did you find those files?

The name setupact.log is used in different places so the file you found may not be the log of your windows installation.

For instance, I have an almost identical file in a C:\Windows.old\Windows folder, but I don't think that is the log of the most recent windows installation on that machine (which was a successful one).

The relevant log files are more likely to be in
Code: C:\$WINDOWS.~BT\Sources\Panther[/quote] And I'd also expect the setupact.log to be a lot larger than the file you found.

 

And I'd also expect the setupact.log to be a lot larger than the file you found.[/quote] I found the correct file going by your directions. However, when I try the upload using "Manage Attachments", the little circle spins for a while, but the file never appears in the box so I can drag it to be attached here. I have tried it several times. The file is 33.1MB.

BTW, the file in the folder has blue letters for the name. That's strange to me.

 

If File Explorer has blue names for files or folders it shows that they are stored with ntfs compression.

Compress or Uncompress Files and Folders in Windows 10

 

There's a size limit on attachments. It appears to be 2MB for .log files. Try sending your file to a compressed (zipped) folder first, the limit for .zip appears to be 8MB.