|
Posted by John Doe on June 3, 2008, 11:04 am
If you were Registered and logged in, you could reply and use other advanced thread options
autoruns, etc.
It's in the boot sequence somewhere; can anyone knowledgeable about the XP
boot sequence shed any light on this? Where can I start looking for this
reference & remove it?
STOP: c0000135 {Unable To Locate Component}
This application has failed to start because baseokfrf32 was not found.
Re-installing the application may fix this problem.
> Try msconfig.exe to avoid running this file at start-up.
>
> If you are unsure how to do this a web search for msconfig +windows
> +startup
> will find you a tutorial on troubleshooting start-up problems.
> --
> Regards,
> Newell White
>
>
> "John Doe" wrote:
>
>> There is some sort of infector going around that injects itself into the
>> boot sequence of XP that randomly names itself "base????32" (where the
>> last
>> 4 or 5 letters are random, but the first 4 are always base & the last 2
>> are
>> always 32) & causes the machine to fail on boot up because it cannot find
>> this file:
>>
>> STOP: c0000135 {Unable To Locate Component}
>> This application has failed to start because baseokfrf32 was not found.
>> Re-installing the application may fix this problem.
>>
>> This usually occurs after removing the winantivituspro infector (clearly
>> the
>> anti-malware people haven't figured out how to remove this properly
>> yet!).
>>
>> Any ideas on how to repair this issue without having to do an XP repair
>> install? Or where XP gets the command to look for the file? I can't
>> seem
>> to find a "boot.sys" or any such file that references it, and obviously
>> can't go into the registry to look for it . . .
>>
>> I've tried going into the Recovery Console & doing fixboot, fixmbr,
>> chkdsk
>> /p /r etc but no good.
>>
>>
>>
>>
| 
XML site map