Windows won't start after auto update

I read the FAQ and Googled, but I just haven't been able to find a solution. This is an antique system, but it's the one I prefer using, so I hope it's so old that everyone knows how to solve problems in it.

Modified hp Pavilion 325c HDD; almost all other hardware changed years ago
WinXP-SP3, auto updates (can't remember if it's Home or Pro)
Spybot auto updates auto scans scheduled
Avast auto updates auto scans scheduled
CCleaner auto

I rarely boot the machine, but last night it seemed slower than normal, so before bed, I booted. I barely noticed the pending update symbol on the shutdown menu, and just hit restart before immediately turning the monitor off. I had just been browsing forums like this as usual (no installs in the past few days or any porn/gaming/P2P sites), so I can't think of anything I did that would have caused a problem.

This morning, I found a blank desktop with a warning window saying the procedure entry point ReleaseSRWLockExclusive could not be located in KERNEL32.dll . Clicking OK (the only option) brought an almost-identical warning, this time about ObjectStublessClient29 in ole32.dll . Clicking OK there causes the system to reboot. My BIOS appears normal. LastKnownGoodConfiguration produces exactly the same results. SafeMode does too. I can get into the repair console using a W2KP install disk, but I don't really know what to do once I'm there. Being familiar with the VERY early versions of DOS, I'm surprised the reported file sizes for C:\io.sys, msdos.sys, and several other critical system files is reported as 0, and the TYPE command says they can't be opened, but IDK if that's a significant part of this problem. I never had an XP install disk for this machine since it was a return/clearance at my local Sam's Club.

I have to assume the Windows auto update caused this, but can you confirm it before I go thru the hassle of fighting MS over it? Is there an easier fix?

I have a Win2KP-SP4 system, but it has been even slower over the past year or so, and I only use it for e-mail & background music. Currently, I'm using a Vaio PCV-RS710G running WinXPH SP3 (similar to the problem machine). It was bought new full-retail and hasn't been modded, but I can't remember if I have install disks for it. I have a Sony recovery DVD Ver.V128.0 for it.

 

My posting rules say I can edit my posts, but I don't see a button for it...

Anyway, it turns out the slower system is running XPP-SP3; not W2KP-SP4.

I've also found C:\windows\system32\kernel32.dll and ole32.dll, and their reported filesizes are ~1M each. Kernel's date is '09, and ole's is '11, so they don't appear to have been replaced recently. There are several hidden subdirectories of C:\recycler including nprotect (isn't that a Norton folder?) containing a lot of .DLL files, but their names have been changed to numbers so I can't easily see if any of them is a previous version of the indicated files.

 

On another BBS, I was advised to read this page:
http://technet.microsoft.com/en-us/library/bb457123.aspx

I think my problem is occurring AFTER the logon phase begins, but I'm not sure if a successful logon is completing. I use the MS PowerToy TweakUI for auto logon.

THANKS, MS!!! I'd love to do both of those, but I don't really know what to do.

The instructions appear to assume that safe mode works, so I'm not sure I can do this, although I think it might work if I could. But it's not clear to me what that step is dependent on. There's no clear division in that document for what step follows what, and what follows a NEGATIVE response to a particular step.

System restore instructions also appear to require that safe mode functions, and mine doesn't, so I don't know if I can manually (thru DOS) restore the registry from a previous version.

This looks promising:

Will that work for me? I don't want to try it without some confirmation that it's appropriate & safe for my situation. This makes me think it might NOT:

Mine never appear.

And I'm VERY worried about attempting to edit the registry thru a DOS prompt (if that's even possible) instead of thru RegEdit. If it comes to that, I'd probably rather JABOD the HDD into another system to pull my data off, and then start with a clean install.

At this point, I'm about halfway down that page, and every step seems to presume that I'm in safe or normal mode (which I can't get to) as opposed to recovery console (DOS), so I'm taking a break until I get more feedback.

 

Hey Steve...just a quick comment, while I attempt to think through your circumstances a little bit.

On the updates issue...Since they have to be there, and really there isn't anything wrong with them, I think it's best to consider that the problem is not them specifically. I think what's happened is you have some corruption in Windows either from removing files (i.e. using CCleaner...more below) or from installing and then later removing a program that made some unacceptable changes to Windows, leaving the OS in a non-functional state without the program. Weird how these problems can show up. Just uninstalling the program might not cause the problem. Insttead, no problem until you click on a program that shared a file with the one you removed and bam a system error. It leads to boot problems and all kinds of other conflicts too frequently affecting Windows system files.

I had a program that I trusted that removed the entire Windows Installer. That was interesting I must say and a real learning experience. I started to get how the dependencies are arranged in Windows a little bit. Alot of it depends on records kept in and created by Windows Installer during the Windows installation process and during the installation process for each program. There are other important Windows records, too.

On to CCleaner. This is why I recommend using extreme caution with CCleaner. I know, I've heard it too before, but I think it's real. I mean, CCleaner is removing Windows logs and other system files and altering the registry including removing .dlls (data dynamic link libraries). These are files that help programs link to other programs as they should and find things like Flash or Windows components. For the most part maybe that's OK, but it doesn't take much to break software dependencies as I learned the hard way. I use CCleaner just to remove temporary internet files from browsers and occasionally to set the start up programs, but that's all for me. I really do think it could have something to do with this problem. NOTE: I guess I would recommend Comodo System Utilities for registry cleaning. I usually just wait until I can't go a second more (maybe every 5 months) then run the CSU and have it remove based on the minimal scan (mildest setting)...

Just a note on Recovery Console...I think you'd actually have to have copy of the file to replace if you were going to replace/copy over a file using the interface. Mostly for trained techs I think...

Gonna think for a while on your issues. Interesting that you'll have a nice 3 PC set up. Might really pay off big time for you to get a copy of Windows XP Pro...

 

I have CCleaner configured NOT to mess with Windows logs, so that's not it. And no matter what I uninstalled, that couldn't possibly cause something else to ask for an entry point that never existed in the kernel. Only a faulty Windows update could do that.

 

Hey, Steve

OK...I get where you are coming from. Googled ObjectStublessClient29 and found this from MS about your exact problem:

http://answers.microsoft.com/en-us/...9e?msgId=66280800-d6b1-47f6-bf98-da6dd3df836e

I have my doubts about this based on the comments on the above page...

Here are the actual instructions in case you have trouble finding the link:

http://support.microsoft.com/kb/307545

A little surprised there isn't a patch that I see here or Hotfix for this...

 

This looks like it might be worth a look:

http://www.ehow.com/how_5173447_replace-oledll.html

How to replace ole32.dll...

 

Hi,

I was just going to say do a chkdsk from recovery console just to rule out a problem with the filesystem. Sometimes Windows says a file is missing when it is really still there.

See if it will take the /f switch and if not do the chkdsk /r.

chkdsk /f
chkdsk /r

 

The first link only works in Windows; I can't get to Windows; only DOS thru the recovery console.

The 2nd is for replacing OLE32; my OLE32 exists, and hasn't been modified in years.

Chkdsk is for file system errors; my file system is fine - I can browse it in DOS, and my system gets all the way to the desktop background. No file is missing - but something that Update did is asking for a version of OLE32 that doesn't exist in XP.

So thanks, but none of those applies to my situation.

 

ole32.dll - Microsoft OLE for Windows is a DLL file provided by Microsoft Windows Operating System. OLE stands for Object Linking and Embedding.

There is a file by the name of OLE32.dll on Windows XP machines. On mine it is version 5.1.2600.6168, which the standard one for Windows XP SP3 32 bit machines. Apparently, it can become corrupted. Do you have access to the file through recovery console to see its size?

Microsoft lists its size as either 1,288,704 KB or 1,289,216 KB. I have the first one on this machine I'm using right now.

I saw that one of the possible MS errors associated with this file is "C0000221 (Bad Image Checksum) The Image ole32.dll is possibly corrupt". This tells me that this file could be corrupted. However, this user used the Recovery Console to attempt a repair of the file. It did not work. But, it couldn't hurt to try if you can get the file as its size does not change and since MS seems to believe it can be corrupted...

I do think you have a good leg to stand on for a claim with MS that their update caused the problem. But I am more leaning toward believing that they'll just blame your web use that night or whatever for the problem and try to dismiss it. I'd like to know which update it was. I just made and update today of 3 things. The Malicious File Tool I'm sure was OK. I think the other two were MS Office.

 

Steve: Don't know if this will tell you anything from a Google search of "What does SRW Lock mean?":

ReleaseSRWLockExclusive is located in KERNEL32.dll. That was the first error that ReleaseSRWLockExclusive could not be found. Best I understand, something must have made a request for a SRWLock, but that part of KERNEL32.dll showed up missing.

LOL about this message left for anyone with the ObjectStublessClient29 could not be located in the dynamic link library ole32.dll error:

http://www.fixya.com/support/t11176748-procedure_entry_point

Here's an interesting page showing all the functions in ole32.dll:

http://www.softspecialists.com/.\library\genlib\7\ole32.htm

I guess I'm leaning toward a problem in Kernel32.dll of some kind or a hard drive problem. The only thing I can think of is to try to find an XP Pro retail installation disk and run the repair install option. If you can access your Win2K disk maybe you can get into a Windows XP disk to run a Repair Installation...

 

Steve03...
One more thing. Here's a 9 page walkthrough with someone who seems to have had the EXACT same problem as soon. This person was having to boot from a Kaspersky disk, but the system crashed in the same way with the same error:

http://www.bleepingcomputer.com/forums/topic406571.html/page__st__15

 

You're still not getting it. Those entry points don't exist in XP.

So my files are not corrupt. A new process has been added at startup that should not be on my system. And the only thing that got installed was the WinUpdate.

That "bleeping" link isn't vaguely like mine - he has malware; I never had (and still don't) any indication of malware. He gets BSOD; I get the desktop background.

 

10 minute time limit on editing...

I never use P2P or browse pr0n or gaming sites. I don't download BS; only a few verified programs; usually either directly from or at least recommended/approved by MG. I keep all my protection updated & running.

 

How hard is it to run a chkdsk and PROVE that your files aren't corrupt? Just rule it out. No corruption and it will take 15 minutes.

Random problems with random files and yet you refuse to run a chkdsk? Good Luck!

Albo is nicer than I am.

 

Steve03...

You may or may not have a virus on your problem PC, but the 9 page resolution to what appears to be identical symptoms, including the mention of a OLE32.dll error, has convinced me that you should treat it as one. Not saying you did anything you shouldn't...just saying that I think something may have gotten by your system's security at a normal seems safe internet site, etc...maybe e-mail if you import those. It can happen.

I think if you treat this as potentially a malware problem and take it to the malware board, you will get your computer fixed irregardless of what specifically caused the problem...

 

I use the XPP system for e-mail; this system has only been used to check/delete e-mail thru Mail2Web.com .

Chkdsk /r is running; I found an XPP install disk, but it requires the admin PW for repair console access and I don't remember it or never had it (used system), so I'm still using the W2KP disk, and it doesn't have chkdsk /f.

 

Chkdsk /r reported that it fixed something, but didn't specify what. No change to the warnings or boot loop.

Someone sent me 5 replacement files (lsass.exe, winlogon.exe, shell32.dll, & 2 other DLLs), and after trading them in, I get a stable but EMPTY desktop. I can even open TaskManager, switch tabs, and open a browse dialog box. I couldn't start RegistryMechanic, but I did notice that TomTomHome was running.

That's a recent install, but I can't remember how many times (if any) I've booted since installing it. I got it for Xmas, so that was probably installed on the 26th, and I don't specifically recall any boots since then, but that doesn't mean there weren't any, or that there were. Anyway: I ended that process. Is there a way from my current situation to prevent it from starting at the next boot? I wouldn't even mind uninstalling it, if I can make that happen. Explore.exe is NOT running, and I haven't tried to manually start it.

 

Good...at least you got in. You were right about the Recovery Console. I had a feeling about it, but I knew I couldn't help you. At least I guess that's how you installed the files that were sent to you.

You said you have CCleaner. You can turn off the automatic startup on your TomTom program using it. Open CCleaner and click on the "Tools" tab on the left. Then choose "Start Up". Find the TomTom process and left click on it. Then right click and select "Disable". That should do it for you. On your next boot it should be off...

 

When I said "empty", I meant it. No START bar; no desktop icons; nothing clickable. I got to TaskMan using Ctrl+Alt+Del, but very few things will actually run. I have to click "NEW TASK", then fight through a dozen identical warnings (tskmgr.exe...Stubless...ole32...) before I can click BROWSE and dig thru the HDD to find something, or if I try to type, I get a dozen or two MORE warnings; sometimes for each letter as I type. Then when I hit OK, another dozen warnings, then maybe whatever I tried starts. If not, another dozen warnings before I can try something else.

Add/Remove Programs WORKS (and I uninstalled TomTom)
Explorer.exe NOT
User Accounts NOT
Spider Solitaire WORKS
FreeCell WORKS
sysconfig WORKS (but is pretty useless since 3 of the files are empty)
msconfig NOT
CCleaner NOT
Spybot NOT

But booting still gives me the empty desktop and access to TaskManager with VERY few useful Windows programs able to start.

 

You need to add more files from the console. Maybe that's all there is to it. Or can you possibly add them from a CD/DVD? Have to find out which ones if that's the way to go.

If you choose to go the malware board way...they'll fix it fast now...or at least faster.

Have you tried booting to your XP disk yet?

 

I don't have a live XP disk, so it only boots into the install console. But after trying several other suggestions from another forum, I gave up. I formatted a spare HDD & I've been installing/updating it for the past couple of days now. When I get everything up, I'll reconnect the crashed drive, try to scavenge all the data off it, and then try to figure out what happened to it.

 

OK...good luck Steve83

 

I finally got around to reconnecting that drive & scanning it. Avast found that Java bug, so that might be what crashed me.