Cannot upgrade Windows 10 preview from build 10130 to 10158 -10162. spontaneous reboot. No logs.

[Bob Tucker]

I downloaded the upgrade to builds 10158, 10159, and 10162 as they became available from Windows Update. This went went well in each case. I removed (uninstalled) the antivirus (bit-defender), rebooted, and tried to upgrade to each build. Each upgrade attempt failed in the same way: The upgrades downloaded and configured rapidly. The upgrade process began to slow badly at 22% complete with 74% of files copied. The laptop spontaneously rebooted when the upgrade process was at 23% with 79% of files copied in each instance, and build 10130 was automatically restored in each such instance. The hidden directory was removed, and no setup logs remain. I made an ISO for build 10162 last night and tried it. I achieved the same results. Can you direct me to information on how to create and recover setup logs in such an instance? I was able to install and upgrade earlier builds without a problem. The laptop is a 2015 HP 15 Notebook PC model 15-g210AU. (I am in Thailand.) It is a PC my wife uses. It has an AMD P6 Quad-Core. Help would be very much appreciated.

 

[ven07]

I can't help you with what you're looking for specifically, but did you try creating another user account on the device? Try that and give the UA full admin priviliges, then proceed to install the new iso via that account.

This might or might not help, but it's worth a shot right? unless someone else actually has a solution

 

[frank pik]

try looking up altering the registry . As long as you're in the right place then you really aren't going to mess anything up for your system and as long as you keep a record of what you're changing then you can always manually change back to how it was before. I
had to change it on 2 separate devices on different update versions. I can't recommend particular registry edits because it took a few different attempts till I found the right ones that worked and it may need different changes on your system.

It's likely going to continue preventing you from updating or getting any fix since it's likely not giving you permission to download since it messed up and either denying your permission or the permission is just not there entirely which means you'll have to either try granting it to yourself (by changing a "0" to a "1" in the best case) or worst case experiment adding a few lines to the registry until you get the right ones from some of the online solutions (which you can copy/paste or add/delete with minimal fuss).
Since it's likely you won't be able to download a fix, your other option will probably be rollback or reinstall Windows 8 to try again with a more stable current build

 

[Subhayan Gupta]

hallow everybody,

I want to install Build 10162 over Build 10130 but without fresh installation. What should I do?
If I just install the the build after mounting the .iso, will the already installed files deleted forever?
Please help.

 

[David Feifer]

hallow everybody,

I want to install Build 10162 over Build 10130 but without fresh installation. What should I do?
If I just install the the build after mounting the .iso, will the already installed files deleted forever?
Please help.

no, If you run the setup program from the root of the iso you are performing an upgrade and it should keep all your programs, files and settings.

 

[Guzzler3]

You know, from being a previous beta tester, the one rule I've always followed (and was told to do by MS) was to do a fresh install of newer builds.

Or revert back to the previous O/S, and then try the upgrade, for that type of testing (I.e. W7 to W10, or W8.1 to W10). To do so we were asked to take a disk image of 'daily driver' system, and then perform an upgrade. Report what worked, what didn't. Then re-image the system back for the next build and testing.

But doing upgrades of various builds was, and always will be, a bloody nightmare. To much fragmentation in the code and settings to make it an acceptable test. I don't know why MS hasn't emphasized this on this operating system. :shocked: