Re: A patch is preventing the system from starting. - Which one?

=?Utf-8?B?VGhhbGFkb3I=?=

So even though the OS knew that a patch was preventing the system from
starting, it can't tell me which? This seems absurd to me. You advice tells
me to redo each patch, reboot and hope it doesnt blow up. While it may be an
answer, I was hoping I can determine which one is the problem

"Mark L. Ferguson" wrote:

> You are probably using a hardware driver that can't handle one of the
> patches. About your only choices are stop using the driver or the patch. You
> can easily select one patch at a time to test, using system restore to go
> back on failure. "Safe Mode With Command Prompt" will accept the command:
>
> %systemroot%\system32\restore\rstrui.exe
>
> You can also try to detect the problem using the error reporting available
> in the Windows Update app. When you 'view update history' you get a link to
> troubleshooting help.
>
> If an error has occurred, it will be displayed with an error code that you
> can use to search online for help.
>
>
>
> --
> Use the "Ratings" feature. It helps the new users.
> Please use the Communities guidelines when posting.
>
> Mark L. Ferguson MS-MVP
>
>
> "Thalador" <> wrote in message
> news:...
> > So I am a good techie and patch my system regularly. I am running Vista
> > x64
> > Ultimate SP1. Up until a few weeks ago no problem. I log on and windows
> > update says I have xx patches to install. I install and reboot and the
> > problems began. When I would try and open MMC, Explorer, IE it wouldn't
> > open
> > or I would get a "Cannot create blank document" error. Tried to go into
> > safe
> > mode, blue screen..Things kept getting worse until I got Stop errors..
> >
> > So I get my Vista DVD and do a repair. It goes through and towards the end
> > the log shows
> >
> > Root cause found:
> > ---------------------------
> > A patch is preventing the system from starting.
> >
> > Repair action: System Restore
> > Result: Completed successfully. Error code = 0x0
> > Time taken = 144676 ms
> >
> > My OS is back to working.. BUT, Windows update now shows I have 14 patches
> > to install. You can believe me I am not installing anything now. So, how
> > do I
> > tell which patch prevented my system from starting?
> >

Colton

Thalador,

Some times you have to do outrageous things in order to find out what is
going wrong. Even if this does mean having to install or remove and then
restart over and over. The only way you're going to find out anything
specific is if the Windows failure leaves you an error file that you can
catch some information from. You said that it can't tell you what is
failing, so this is probably a lost cause; forcing you to return to the only
thing that will work, and that is trial and error. Unfortunately, computer
problems aren't always click and fix, as I'm sure you know. If not, you will
learn soon enough, lol.

Sorry that you are having this problem, bud. The only thing that I can tell
you to help you any farther is to check the updates that you are installing
before you install them. Make sure they are compatible with your system and
devices before you install it. I've had a couple of updates that had my
computer crippled for months, but are no longer an issue thanks to
reformatting and watching what I installed. The only way you will be able to
tell what patch (aka update) is effecting your system, you should do what
Mike advised, and try installing them one by one. Maybe two by two, so you
can move a bit faster, as I know there can be a lot.

--

Colton, PHP/VB6/HTML/CSS/Javscript/IIS/Apache
OS: Vista Home Premium x86 SP1

-
-


"Thalador" <> wrote in message
news:...
> So even though the OS knew that a patch was preventing the system from
> starting, it can't tell me which? This seems absurd to me. You advice
> tells
> me to redo each patch, reboot and hope it doesnt blow up. While it may be
> an
> answer, I was hoping I can determine which one is the problem
>
> "Mark L. Ferguson" wrote:
>
>> You are probably using a hardware driver that can't handle one of the
>> patches. About your only choices are stop using the driver or the patch.
>> You
>> can easily select one patch at a time to test, using system restore to go
>> back on failure. "Safe Mode With Command Prompt" will accept the command:
>>
>> %systemroot%\system32\restore\rstrui.exe
>>
>> You can also try to detect the problem using the error reporting
>> available
>> in the Windows Update app. When you 'view update history' you get a link
>> to
>> troubleshooting help.
>>
>> If an error has occurred, it will be displayed with an error code that
>> you
>> can use to search online for help.
>>
>>
>>
>> --
>> Use the "Ratings" feature. It helps the new users.
>> Please use the Communities guidelines when posting.
>>
>> Mark L. Ferguson MS-MVP
>>
>>
>> "Thalador" <> wrote in message
>> news:...
>> > So I am a good techie and patch my system regularly. I am running Vista
>> > x64
>> > Ultimate SP1. Up until a few weeks ago no problem. I log on and windows
>> > update says I have xx patches to install. I install and reboot and the
>> > problems began. When I would try and open MMC, Explorer, IE it wouldn't
>> > open
>> > or I would get a "Cannot create blank document" error. Tried to go into
>> > safe
>> > mode, blue screen..Things kept getting worse until I got Stop errors..
>> >
>> > So I get my Vista DVD and do a repair. It goes through and towards the
>> > end
>> > the log shows
>> >
>> > Root cause found:
>> > ---------------------------
>> > A patch is preventing the system from starting.
>> >
>> > Repair action: System Restore
>> > Result: Completed successfully. Error code = 0x0
>> > Time taken = 144676 ms
>> >
>> > My OS is back to working.. BUT, Windows update now shows I have 14
>> > patches
>> > to install. You can believe me I am not installing anything now. So,
>> > how
>> > do I
>> > tell which patch prevented my system from starting?
>> >