Slow boot: Hangs at mup.sys then continues...

  • Thread starter Thread starter WATYF1
  • Start date Start date
W

WATYF1

I'm working on a VIAO laptop that has a slow boot-time. During normal
boot mode, it goes through the typical steps before showing the login
screen (applying networks settings, applying user settings, or
whatever)... and on each of those steps it hangs for a good while. But
eventually, it loads the login screen.

If I boot in safe mode, it loads all the services then gets to mup.sys
and just sits there for a while... then it continues to the login
screen.

I'm thinking the problem is not mup.sys, but rather what happens right
after that... the problem is, in safe mode, not much is being loaded,
and yet it still hangs for a while.

The only possible hint I have is that the user said this started
happening after their laptop was added to the domain at their office.

Any ideas on what might be causing this?


WATYF
 
I'm working on a VIAO laptop that has a slow boot-time. During normal
boot mode, it goes through the typical steps before showing the login
screen (applying networks settings, applying user settings, or
whatever)... and on each of those steps it hangs for a good while. But
eventually, it loads the login screen.

If I boot in safe mode, it loads all the services then gets to mup.sys
and just sits there for a while... then it continues to the login
screen.

I'm thinking the problem is not mup.sys, but rather what happens right
after that... the problem is, in safe mode, not much is being loaded,
and yet it still hangs for a while.

The only possible hint I have is that the user said this started
happening after their laptop was added to the domain at their office.
Click to expand...

Since it happened right after being joined to the domain:

1. Check the domain and laptop DNS settings. If you don't have access to
the server, ask the company's IT people - the server should be pointing
to itself for DNS with forwarding zone(s) set up for Internet access
and the workstation(s) should only be pointing to the server.

2. Make sure there are no inaccessible/nonexistent network shares.

Malke
 
Back
Top