Infinite reboot loop after a BSoD and attempted windows updates

Kaktussoft · 16 Jul 2014

Sk8kidamh said:

Got it. Internet works now. Now what?

How did you fix that?

Kaktussoft · 16 Jul 2014

Sk8kidamh said:

Kaktussoft said:

Exclamation points by:
SDA standard compliant SD host controller =>that's a SD-card reader. Totally irrelevangt now.

"Apple mobile device Ethernet-virtualbox bridged networking driver miniport"
Cisco anyconnect secure mobility client virtual miniport adapter for windowsx64- virtual box bridged networking driver miniport
Dw150 wireless-n WLAN half-mini card - virtual box bridged networking driver miniport
Intel(r) 82579LM gigabit network connection - virtualbox bridged networking driver miniport
Microsoft virtual wifi miniport adapter - virtualbox bridged networkijg driver miniport

All virtual and virtualbox stuff? Post screenshot of device manager. Rightclick on Intel(r) 82579LM gigabit network connection->properties. in field status... what is the error code?
Same for Dw150 wireless-n WLAN half-mini card.

The error for both devices is "windows cannot load the device driver for this hardware. The driver may be corrupted or missing"

The two devices with arrow down sign in front: they are just network adapters that are disabled in "network center"->adapter settings.

normal wireless and wired networking looks like normal. Try "windows update"-> find updates. and install 1 as a test.

Sk8kidamh · 16 Jul 2014

Well luckily I still had the setup file for virtualbox, so I used that to remove the install. As soon as I did that the internet connected.

Sk8kidamh · 16 Jul 2014

I had to reboot the computer and it went back into the loop. The registry value that I changed earlier had reverted to 2. Once I switched it back to three again it booted, but I'm pretty sure that if I reboot it's going to keep up with this problem.

Sk8kidamh · 16 Jul 2014

I also can't run sfc /scannow. I'm getting the same error I was getting from the recovery window "There is a system repair pending which requires a reboot to complete"

Kaktussoft · 16 Jul 2014

Sk8kidamh said:

I had to reboot the computer and it went back into the loop. The registry value that I changed earlier had reverted to 2. Once I switched it back to three again it booted, but I'm pretty sure that if I reboot it's going to keep up with this problem.

But did you install 1 windows update?

So with start=3 it boots fine. Also with start=4 (that's what we did before).

Just before shutdown or restart check the value in registry. Or reopen services.msc and look at the start type. It should be manual.

Fixing the value in recovery environment makes the system bootable. So it's definitely not reset in the boot fase.

Try to logoff/logon... is the value reset?

Sk8kidamh · 16 Jul 2014

Well the value for start in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\TrustedInstaller is 2 now that I've booted. The Window's installer module was changed to automatic, but I definitely set it to manual before I rebooted last time. I just finished installing an update, so I'm about to restart to see what happens.

Sk8kidamh · 16 Jul 2014

Okay, so if I reset the registry value to 3 before the reboot, it reboots and everything looks fine. But every time I boot up the registry value is reset to 2.

I installed a window's update and that seems to have gone fine.

Kaktussoft · 16 Jul 2014

After installing an update and just before shutdown: What is the "start" value?
Don't shutdown at that moment but logoff and logon: What is the "start" value?

Sk8kidamh · 16 Jul 2014

The start value is 2 as soon as I boot up, through all of that, and when I shut down. The only time it isn't 2 is if I go into the services.msc and change trustedinstaller to manual.