After 1/8/13 up date system won't boot after login.

I have a relatively new new Dell win 7 64 bit machine. I was using the auto update option for msft updates.

Since the 1/08/13 update and upon first boot in the am it won't complete the booting process after I enter my password. It just spins.

After the first event of this I turned off the auto update. My machine is shutdown at night.

When I use system restore to restore the system to the state prior to the 1/08/2013 updates, and then reboot and then re update the machine it reboots normally. In other words, after it gets to the log in point and I enter the log in then it competes the boot and my desktop is normal.

I can restart it and once again after thing is normal.

When I come home at night I can start the machine and everything is normal.


This is the third morning in a row that upon first start in the AM it won't complete the boot after the log in screen. Just spins.

This is the third morning in a row that I have had to restore the system prior to the 1/08 update, and then reinstall updates in order for the machine to complete the boot process.

I have office 2010.

Any ideas on what is in the 1/08 update that is causing this??

Thank you,

JF.

 

http://www.sevenforums.com/windows-...oft-security-bulletin-s-january-8-2013-a.html

I would do it manually not on auto.

 

Greetings, jficquette, and welcome to MajorGeeks...

Not real clear about your symptoms - does your machine boot normally if you turn off Automatic Update?

Regardless - try turning off auto updates, see if your symptoms change. You might also consider rolling back (via System Restore) to a point previous to the date you've been trying.

 

For the last three mornings it has only booted normally after I system restore immediately prior to the 1/08 update.

After the system restore I have been reapplying the updates manually. After the update the machine will boot normally.

After it's "fixed" I shutdown the machine and go to work. For the last 2 days when I have come home from work about 10 hours later it will boot normally.

When I go to bed at night I shut it down as a matter of habit.

For the last 3 mornings when I have gotten up I have booted the machine to boot to check mail, news etc but it won't complete the booting process. It brings up the login screen but just spins when I put in the the password.

For the last 3 mornings I have had to restore to just prior to the the 1/08 update for it to boot normally.

For the last 3 mornings I have reapplied all of the recommended updates manually, after which it will boot normally. I did 3 shutdowns this AM to see if it was working OK and it booted normally. I shut it down as normal. I am at work now.

I will turnoff the auto date when I get home today. My question is, an update is an update right? Why should it matter how the update gets applied?

Also any ideas what is causing this?? I guess I am wondering if there is an update that is conflicting with my registry otherwise, why would it not complete the booting process after I put in my password and hit enter? I don't know enough about this to know which updates to pick and choose to prevent it, if it is an actually update that is causing it.

Thanks all. I really appreciate it.

John

 

Obviously one (or more) of the updates is clashing with something. You're probably going to have to try to isolate which updates are causing the problems by manually updating, one at a time. Sounds tedious, but it shouldn't be too bad.

Might help if you post a list of the updates in question.

 

All of the Jan 08 updates. 14 total the last time, was 15 but I didn't apply the non windows update this morning. I think it was something to do with office.

Just assuming its one update would take 15 days and if you start mixing and matching then it could take 225 days. LOL.

John

 

This machine had 18 months of free McAfee's when I bought it. First thing I did was uninstall McAfee's and put NOD 32 on which I have used since it first came out years ago.

Thank you for the reply.

JF

PS. On 1/08 I did apply some optional updates. One of which was for the mouse. Since then I did not reapply the optional updates. Also this series of updates had net frame updates.

 

Hello,

Not to put to fine of edge on this but I reboot in safe mode to do the system restore.

JF

 

Your symptoms are somewhat confusing, at least for me. Can't see the "225 days" thing: normally on problem machines I download updates in batches, then install them one at a time to find a culprit. Takes several hours, but not several months.

Did the machine come with any Windows disks, restoration disks, etc. - or did you create your own? The reason I ask: if you've got a valid Windows disk you might run a System File Check to verify system integrity.

If no Windows disk but if you've got restoration disks, and since this is a relatively new machine, if it were mine I'd consider reinstalling the OS and starting fresh with a pristine Windows - then monitoring the manual downloading of any Windows updates.

 

It is only doing over night which so it would take a day to check each update. May not be one update by itself. Could be combination of updates. So 15 x 15 would be possible combinations to test.

It's a Dell purchased from Microcenter about 8 months ago. Not really a problem machine since this is the first issue I have had.

The problem is after it gets to the log in screen and the password is given the desktop doesn't come up immediately which is the normal behavior. It only sits there acting like its trying to load whatever completes the process. I have given up to around 5 minutes to complete. Can't bring up task manager to see what the behavior is of the running processes. I have to unplug/plugin the machine to reboot into safe mode.

Thank you for your reply and attempt to help.

JF

 

This AM I had the same issue again. Wouldn't complete the boot process.

This time however I created restore point as of last night post updates and used that for the restore point after booting into safe mode this morning.

After the restore process it booted up fine. Maybe the updates were just not the factor.

I bought an extended warranty from Microcenter and I guess I will just take it up to them. It must some type of file corruption.

Thanks all for you help.

JF

 

Sorry you're having to go through this, but since you do have the warranty then that might be the best route to take - it is extremely difficult to troubleshoot a problem such as yours remotely.

Good luck - please keep us posted.

 

Go ahead and run a chkdsk to rule out corruption.

Computer>right-click the C: drive and select Properties. Under the Tools tab choose Check Now. Leave the first box ticked and hit Start. It will schedule for next reboot. Reboot and let it run. See if it helps after the next time you turn it off for the night.

 

Thanks man. It's a learning experience for sure. I may shutdown tonight with Nod 32 set not to start automatically and see if that helps. I mean it feels like there is some file that is not being processed or being blocked from being processed. Maybe some nod 32 update is causing the problem. If that doesn't do it then I will take it up to Microcenter tomorrow.

I will let y'all know what the deal is.

Thanks

JF

 

I scheduled it last night before I shut it down. It ran when I booted up today. After the restart the desktop came up as normal. Maybe it's resolved. I will shut it down later today and see if it comes back up.

Thank you.

JF

 

I wish this thing would just catch on fire. I reboot it just now and let it spin while I was in the shower. Still no boot. I yanked the power cord out. Cranked it back up in normal mode, damn thing is up now.

I have a life sized picture now of me dealing with the morons at Microcenter trying to explain this.

John

PS. This machine is an XPS 8500 with the 32 gb ssd wired into the mother board. 3770 chip, 12 gigs of memory. I bet you its the ssd.

 

Good morning...

Do it - no sense beating your head against a wall when you've paid to let someone else bear the punishment.

 

I agree, thanks.

John

 

Hi,

It was malwarebytes causing it. On a lark I decided to not have it start with windows. No problems since.

Also found that this is a rare but not uncommon issue with malwarebytes. Here is a link that discusses it.

http://forums.malwarebytes.org/index.php?showtopic=85053

John

 

I am at work now and don't know what version I have at home when I get home I will check. At work my build date is 12/14/2012, 1.70.0.1100

I didn't even think to go to their forum. I found it after I fixed it and searched to see if other people had had the problem.

I just figured all it was something hanging up. Also I put the exclusions in Nod 32 for mbam and for Nod 32 in mbam. The exclusions are in the link I provided.

John

 

I have the same version at home as at work. The same as you do. No Jan update.

John

 

I guess it was the problem. An regular mbam malware update probably starting clashing with something and it was just coincidental with the Jan msft update.

Works great now.

John

 

Good morning...

Huh - Malwarebytes. Who woulda thunk it. :confused

Glad you got things sorted, jficquette, and thanks for the feedback.