G
Guest
Basically after a few months of running Vista Ultimate, both on my old
computer and my new one, the start menu is oversized and is frozen after
Windows has loaded from a regular boot.
At first it looks like this:
http://www.eeplanet.com/dd/the problem.jpg
Basically it looks like that (expanded in size) when it first starts up. It
won't do anything... if I mouse over it, all you see is the "hourglass"
animation.
I can still access task manager with ctrl alt del, so I end the explorer
process and restart it. When it comes back up, it STILL stays locked up, but
it has returned to the normal width...
This has done this in every computer I have owned.
I thought at first it was my old computer, but now I see it on this one. I
DID figure something out on my old computer though: If I used system restore
to go back to the last update prior to the latest Windows Defender update,
everything works fine again... I then tried to do the update again (defender
definitions) and it happened again on the next boot... So I disabled Windows
update and the problem was solved. I have not tried this yet on my new
computer...
Anyone else had this problem?
computer and my new one, the start menu is oversized and is frozen after
Windows has loaded from a regular boot.
At first it looks like this:
http://www.eeplanet.com/dd/the problem.jpg
Basically it looks like that (expanded in size) when it first starts up. It
won't do anything... if I mouse over it, all you see is the "hourglass"
animation.
I can still access task manager with ctrl alt del, so I end the explorer
process and restart it. When it comes back up, it STILL stays locked up, but
it has returned to the normal width...
This has done this in every computer I have owned.
I thought at first it was my old computer, but now I see it on this one. I
DID figure something out on my old computer though: If I used system restore
to go back to the last update prior to the latest Windows Defender update,
everything works fine again... I then tried to do the update again (defender
definitions) and it happened again on the next boot... So I disabled Windows
update and the problem was solved. I have not tried this yet on my new
computer...
Anyone else had this problem?