Windows 10 1903 reboot loop

[David Anderson]

Hi LinusTechTips forum,

  Microsoft just released their newest and latest Windows 10 v1903 a few days ago. I thought that it would be a good idea to have a clean install because I was getting serious lags. So when I was trying to reinstall my programs and start doing stuff all over again, at the moment when I finished downloading Office 365, I restarted and have a reboot loop. I don't know what to do so I started going into Automatic Recovery and used System Restore. I went back and it was fixed. A few days later, it happened again when I finished logging into my Office 365 account and shutdown my computer. This time, System Restore didn't work. So I had another clean install and it happened again, the same moments that I had before. I tried to clean install twice and didn't work. Aaand I cannot work without Office.

 

Please help,

  David Anderson

[TempestCatto]

We had a similar issue at work. The guy updated his PC overnight (1903) and when he came in the next day, he was stuck at the login screen. His monitor kept flashing repeatedly. I did not try booting into safe mode and use DDU however, maybe try that? The reason I did not try it, is because he's had so many issues I just decided to recover his data, wipe the drive clean, and install Windows 10 Enterprise edition instead of Windows 10 Pro. I disabled the update service in services.msc and he's not had any issues since.

 

Are you able to boot into safe mode?

[homeap5]

Well, most of Windows problems are in fact hardware related problems. I saw computer with somehow broken motherboard that works perfectly with win7, but not win8/8.1, no matter what (USB devices makes system unusable). Sometimes its drivers related, but again - thousand of people has probably 1903 version installed on similar or the same configuration as yours and has no problems.

 

I made two upgrades so far - on i7-8700k with NVidia GPU and on 4th gen motherboard with pentium with integrated gpu. Both without any problems (that was surprising me).

 

In theory improvement in memory management in system can cause problems that reveals after update, because of faulty RAM (or wrong OC). Reinstalling or clean install system is pointless (especially if you're doing it twice). If something is wrong, start with hardware check, not with destroying system. Clean install may gives you false sense that problem has been resolved - for example with well known bug in Samsung EVO 840 serie, clean install can speed up your system, but if you know what was wrong, you know that it was not because clean install itself, but because re-write data to the drive. The same problem I noticed with GoodRam CX400 serie - and I resolved it by imaging system and re-write the same image back to the same drive. This is not your problem of course, but just an example that clean install is not a good way to detect where is your problem.

[David Anderson]

7 hours ago, TempestCatto said:

We had a similar issue at work. The guy updated his PC overnight (1903) and when he came in the next day, he was stuck at the login screen. His monitor kept flashing repeatedly. I did not try booting into safe mode and use DDU however, maybe try that? The reason I did not try it, is because he's had so many issues I just decided to recover his data, wipe the drive clean, and install Windows 10 Enterprise edition instead of Windows 10 Pro. I disabled the update service in services.msc and he's not had any issues since.

 

Are you able to boot into safe mode?

I am able to boot into safe mode because I force-restarted 3 times and it turned on Automatic Repair

[David Anderson]

4 hours ago, homeap5 said:

Well, most of Windows problems are in fact hardware related problems. I saw computer with somehow broken motherboard that works perfectly with win7, but not win8/8.1, no matter what (USB devices makes system unusable). Sometimes its drivers related, but again - thousand of people has probably 1903 version installed on similar or the same configuration as yours and has no problems.

 

I made two upgrades so far - on i7-8700k with NVidia GPU and on 4th gen motherboard with pentium with integrated gpu. Both without any problems (that was surprising me).

 

In theory improvement in memory management in system can cause problems that reveals after update, because of faulty RAM (or wrong OC). Reinstalling or clean install system is pointless (especially if you're doing it twice). If something is wrong, start with hardware check, not with destroying system. Clean install may gives you false sense that problem has been resolved - for example with well known bug in Samsung EVO 840 serie, clean install can speed up your system, but if you know what was wrong, you know that it was not because clean install itself, but because re-write data to the drive. The same problem I noticed with GoodRam CX400 serie - and I resolved it by imaging system and re-write the same image back to the same drive. This is not your problem of course, but just an example that clean install is not a good way to detect where is your problem.

I kind of get the idea you are getting here, but I just replaced my drive to a Samsung EVO 860 Series 3 months ago, my RAM to an 8GB not long ago and I have rechecked my hardware twice and found no problems. I only did clean install because I was stuck at the boot up section and didn't know what to do. I used Driver Booster to download drivers though, does that affect anything because this only happens if I do Windows Update stuff?

[David Anderson]

Thank you, everyone, for their support, but a few minutes ago, I think Microsoft fixed the bug and the error is gone.