I have applied the last two patches in the folder. KB2xxxxxx System will not boot now! C000021a fatal system error, system process terminated unexpectadley. 0XC000012f, System shut down. Have tried a system startup repair, says, A Patch is preventing the system from starting. Can i uninstall these update using CMD on advanced startup repair or anything?
Windows6.1-KB2275828-x64.msu 01-Aug-2010 04:03 1.1M Windows6.1-KB2277956-x64.msu 28-Jul-2010 06:02 6.7M Windows6.1-KB2291175-x64.msu These are the ones i think i installed tried using the wusa.exe /uninstall /kb: method in cmd but keeps saying wusa.exe is not recognised as an internal or external command!
Thanks! I have tried safe mode yet it loads so much then still crashes. I havent tried sfc though. I have installed a 2nd hard drive with xp on, gunna see if i can manually uninstall via a different installation. If not ill try the sfc etc.
and because i installed xp on another drive ive now fooked up my MBR! Need to reset that, as its giving me the cannot update boot config. Thwen hopefully i can try the sfc!
The SFC needs to be run from Windows itself (ideally, as a precautionary tool), from the Windows 7/Vista installation disk (from the command prompt on the installation disk, post startup repair. You may need to specify the path), or from another installation of the same OS on a different drive. Anyways if you run SFC from XP, it won't help you at all. The SFC included in OS's before Vista work differently, and aren't as powerful as a tool. You can't do an offline check from Xp to Vista/7, you can only do an offline scan from a separate installation of the same OS (although I believe a Vista to 7 and vice versa check works). Say if your corrupt OS is installed on Drive 1, and the temporary installation on Drive 2, when you run SFC from the temporary installation you can run it like: sfc /offbootdir=d:\ /scannow or sfc /offwindir=d:\Windows /scannow (assuming the Drive 1 installation now becomes D drive)
Okay, I boot the PC it says, repair PC or boot windows normally, i click the top one, and then it loads up the repair options. Are you saying id be best off inserting the disk, and running the sfc from the disk rather then the repair option on the PC?
Annoying me now, used the repair option on the Windeows 7 disc, command prompt says: X:\Sources, ive tried sfc /scannow, keeps tellin me i need to restart. Saying the best option is to put the XP HDD in and boot into XP, and then use the above. I know corrupt drive is c therefore in Xp under cmd id type. sfc /offbootdir=c:\ /scannow Or wouldn't this work?
Also, Using command prompt off the Disc, i used the wusa.exe etc, and it gives the following installer encountered an error 0x80000ffff catastrophic failure Guess im going to have to reinstall arent i?
If doing it from the Window 7 disk, you need to use the: sfc /scannow /offbootdir=c:\ or sfc /scannow /offwindir=c:\windows command, if you don't specify the /offbootdir or /offwindir, I'm not entirely sure about this but it probably checks the Windows PE environment (that is, the repair part of the Windows 7 disk) rather than checking the installed Windows!
As of 8/1, the links are reversed, with the x86 link giving you the x86-64 version and the x86-64 link giving you the x86 version.
That doesn't want to seem to work either. Guess ill just have to backup onto spare HDD and reinstal Windows on the main drive. Then spend about 10 months installing the update pack from fresh install!
If you can't install last update (KB2286198) and your system falls down, you can do two things: merge all 305 updates with new KB2286198 to installation DVD and upgrade your system at all, or install clean OS from DVD and after that install all updates before any applications. During installation (KB2286198), if you got frozen screen, hard reset your OS and press F8 at boot screen then select boot in "Safe mode" to reverse changes, then you can hopefully boot your OS.
@SoloR was just wandering if KB2286198 was ommitted on purpose-on MU August 2, 2010-or if it showed too late. Thanks, RickSteele
no. Thing is i updated that hotfixes on sunday and this update came on monday, so i didnt add it yet since it feels pointless to add only 1 update ill add it in ~2days or so when ill do next scan of MS database.