So like could I download the windows 7 OS to a USB and then boot from that? Is there another way to repair from the OS, I don't have a CD of it though. It stays at the "windows is starting." screen for like 2 minutes and then goes and checks a disk. UPDATE: Every time I try to boot up my laptop now, it will check a disk and at the end of the check it says no problems were found. I don't know what other information I should include here so ask questions if there is something else you want to know. I have tried booting into safe mode and booting from last known successful boot, neither of these things have worked. I have tried to follow some of the suggestions here and here yet none of them have worked for me. This repair always fails, however I looked under the repair log and it says that it is due to a corrupt registry and has some hexadecimal numbers. Recovered from backup, still in boot loop.Every time I try to boot my computer, it tries to do a system repair. As suspected, after we restarted, it was in the boot loop. We also created an image backup on one of the affected machines before it was restarted. Removed that on a system, still in boot loop. The only other interesting thing we've found is that the affected machines have an "extra" boot entry in SysConfig/Boot. Start-Process -FilePath $file -ArgumentList "/quietinstall /skipeula /auto upgrade /copylogs $dir" -verb runas Here's the script that seems to have caused it: We were able to "recover" a few machines that hadn't been rebooted by manually running the same Windows Update file (via GUI) - they upgrade to 19041 and all is well.Ĭould anyone recommend an offline registry repair utility that might work for something like this? Any other thoughts? Unfortunately these machines did not have System Restore active and RegBack is empty. Disabling automatic restart doesn't work. The system attempts to boot normally, then automatically attempts recovery sequence, then boots again. We can't get into Safe Mode at all, even after bootrec and many different attempts with bcdedit. Unsure exactly why the Win10 update script is causing what we're seeing, but appears to affect machines that were on 18363 and previously upgraded from Win7. After extensive troubleshooting, root cause appears to be registry hive corruption rather than MBR. We have an issue affecting multiple Win10 machines that are in a boot loop after Win10 update pushed via PowerShell script.
0 kommentar(er)
