Here are my specs: Motherboard: Asus P5KPL-AM EPU CPU: Intel Core 2 Duo 2,6 GHz RAM: 4 GB GPU: Geforce 8600 GT 256 MB Chipest: Intel G31 Dual boot windows 10 and os x 10.10.3 Os x boots normally but Windows bootloops while trying to update. It says: updates failed, rolling back changes, rebooting and so on in an infinite loop. After forcing it off manually and rebooting it gave a sad smiley face BSOD saying "BAD SYSTEM CONFIG INFO" and boot loop again I forced it to power off because last time I interrupted the loop this way I managed to get it booting properly, this time it boots for 5 minutes (!!) BSOD's, reboots and loops this way.. Can somebody please help? Really don't want to reinstall cause I've spent 10+ hrs setting up all the drivers, the settings, osx dualboot etc the way I need them. Clean install is the last thing I need..
This Happen Because You Interrupted the Update Process Either Power loss or You Interrupted by your own.... One possibility is Around If You've System restored Than you can Easily go Back to Previous working State...Than Re-update The WINDOWS...
You may not have a choice..... A bad/corrupted update finally caused me to wipe a windows 7 install which was stable for 3 years.... Would try to install update... reboot.... said update failed... reverting... reboot.... repete cycle I did manage to disable the update but you can't in win 10
You misunderstood. It was ALREADY looping but without BSOD. AFTER I interrupted it it started looping with BSOD instead.
You can disable updates in windows 10 too but it needs to be the "Long Term Service Branch / LTSB & Mission Critical System / MCS" version of the Enterprise edition.. Gonna try auto repair from Win10 install iso.. But ALL advice and help is appreciated so, people, please post your thoughts
If you made a restore point you might try boot to media --> command prompt --> rstrui.exe /offline:C:\windows and the last restore point made should reset
which bootloader, and do you use a modified DSDT.aml which gets injected while boot? BAD SYSTEM CONFIG INFO that's typically a result from windows not dealing good with modified DSDT values or variables, had similiar results with ozmosis and DSDT mod. remove DSDT.aml and then it will bootup fine. even I wouldn't boot windows from hackintosh bootloader like chameleon, clover, or any other one, cause the native windows bootloader just doesn't load a modified DSDT.