Vista Control Panel Issue

[melissa]

I'm having a problem in Vista Home Premium where the Control Panel either won't open (see the outline of the box, little blue circle, then nothing) or opens w/ nothing but a blank white background (no icons, text, etc.). Also, the Welcome Center no longer opens at start up.

I found this solution which seems to provide only a temporary fix:

click the round vista button.
where it says start search, type "cmd",then enter.
In the dialog box type "services.msc",then enter
Highlight "Software Licencing" and click "restart" in the upper left corner
Highlight "SL UI Notification Service" and click "start" in the upper left corner
Your done!

http://pcadvisor.co.uk/forums/index.cfm?action=showthread&threadid=295889&forumid=20

I had this same problem, I think it's due to one of the latest hot fixes. Anyways, it is quite easy to fix. Goto start-run "services.msc"

Restart Software Licensing, SLUNotify & Readyboost

That should fix your problem.

http://www.hardwarecanucks.com/vista/2138-vista-control-panel-problem.html

Any thoughts or advice?

 

[Maxxify]

This is a known problem...in fact, it's been around a while, as I first noticed it way back in alpha testing (seriously). I've answered this question before and although I'm not sure if Microsoft has gotten around to fixing it, the temporary solution I came up with is a .bat file you run on start up (as administrator) that will stop/restart the relevant services - it does the same thing the solutions you posted do, just a bit easier to manage.

You should only need to worry about Software Licensing and ReadyBoost, if your OS is activated, or at least I have SL UI Notification on Manual and it doesn't start up.

Anyway, open notepad and write the following:

net stop readyboost
net stop slsvc
net start slsvc
net start readyboost
@cls

Save the file as something.bat

This will stop ReadyBoost first (which depends on SLSvc), then SLSvc, then restarts both in opposite order, then it will close the command window. It needs to be run as administrator. If you need to work with the Notification service, too, for some reason, just add net stop/start SLUINotify in the appropriate places.

 

[melissa]

Thanks for the help.

I also got a "blue screen" before, but couldn't get the exact error since it closed fast and shut down the computer on me. Any way to figure out what it was after the fact?

 

[Maxxify]

Blue screens should be listed in the Event Viewer, which is under Administrative Tools (which can be found in the Control Panel, but can also be placed on the Start menu). The functionality of the blue screen memory dump is handled under Control Panel, System, then "Advanced system settings" in the left pane, and finally "Startup and Recovery."

 

[Guest]

Here is what i got from a "Microsoft Tech help chat". its a joke



Andy has joined this session!


Connected with Andy. Your reference number for this chat session is 1947667.


Andy: Welcome to Microsoft Customer Service Chat, Dave. Please give me a moment while I review your question.


Andy: Please note that this chat service is available to guide you to the appropriate resources for your questions. Often this can include technical support options or a phone number to the appropriate Microsoft team.


Andy: Did you obtain the Hotfix mentioned in the Microsoft Knowledge Base article (929637)?


dave: I started here http://support.microsoft.com/kb/936686/en-us and then went on to the "hotfix"


Andy: Thank you for the information.


Andy: One moment please.


dave: k


Andy: Thank you for your patience.


dave: yw


Andy: I am sorry to inform you that the Hotfix that you need is no longer available for download from Microsoft. I will certainly help you reach the right resources for further assistance.


dave: anything to get the control panel to come up, its affecting other users also...


Andy: Okay.


Andy: As the issue is technical in nature, I recommend that you contact your computer manufacturer for any warranty or no-charge support.


Andy: You may visit the following web link that includes contact information for most of the computer manufacturers, which helps you to locate the contact information of your OEM:


Andy: Page pushed, http://support.microsoft.com/?LN=en-us&scid=gp%3Ben-us%3Boemphone&x=12&y=9


Andy: Dave, is there anything else I can assist you with today?


dave: I thought it was a vista problem not a manufactuer problem?


dave: how could it be a manufacturer problem when it has to do with microsoft's software?


Andy: Alternatively, you may work with a Microsoft Support Professional on a Pay-Per-Incident basis to resolve the issue, by calling at (800) 936-5700, Monday - Friday 5:00 A.M. - 9:00 P.M. Pacific time, Saturday and Sunday 6:00 A.M. - 3:00 P.M. Pacific time.


dave: So you are telling me i have to pay for something that is a problem with your software?


Andy: I hope the issue will be resolved soon.


dave: You and I both, do you guys even have a fix for this?


Andy: Please contact your computer manufacturer for warranty support available for your copy of Windows Vista since Windows Vista came pre-installed on your computer.


dave: wow, thats amazing that you guys are pushing this off on the manufacturer


Andy: As per the agreement between Microsoft and computer manufacturers, the computer manufacturer should provide warranty support for pre-installed copies of Microsoft products on their computers.


Andy: I hope the issue will be resolved soon.


Andy: Thank you for contacting Microsoft Customer Service Chat. Please feel free to contact us again. We are available 24 hours a day and 7 days a week.

 

[aford10]

You obviously have an OEM version of windows. It's the manufacturer's job to support the customer with windows OEM. That's the price the manufacturer pays for getting a large discount in the software purchase.

 

[mentormatt8]

This is a known problem...in fact, it's been around a while, as I first noticed it way back in alpha testing (seriously). I've answered this question before and although I'm not sure if Microsoft has gotten around to fixing it, the temporary solution I came up with is a .bat file you run on start up (as administrator) that will stop/restart the relevant services - it does the same thing the solutions you posted do, just a bit easier to manage.

You should only need to worry about Software Licensing and ReadyBoost, if your OS is activated, or at least I have SL UI Notification on Manual and it doesn't start up.

Anyway, open notepad and write the following:

net stop readyboost
net stop slsvc
net start slsvc
net start readyboost
@cls

Save the file as something.bat

This will stop ReadyBoost first (which depends on SLSvc), then SLSvc, then restarts both in opposite order, then it will close the command window. It needs to be run as administrator. If you need to work with the Notification service, too, for some reason, just add net stop/start SLUINotify in the appropriate places.

I had the same problem and it seems that restarting SL UI service fixed it. However, I my Ready Boost is disabled. I still had to reboot Vista for this problem with the Control Panel be fixed. Any other services that had to be restarted that SL UI maybe depends on or vice versa? See for more details on my solution here: http://annoyances-resolved.blogspot.com/2009/11/vista-control-panel-not-coming-up.html

 

[mikedenney]

This is a known problem...in fact, it's been around a while, as I first noticed it way back in alpha testing (seriously). I've answered this question before and although I'm not sure if Microsoft has gotten around to fixing it, the temporary solution I came up with is a .bat file you run on start up (as administrator) that will stop/restart the relevant services - it does the same thing the solutions you posted do, just a bit easier to manage.

You should only need to worry about Software Licensing and ReadyBoost, if your OS is activated, or at least I have SL UI Notification on Manual and it doesn't start up.

Anyway, open notepad and write the following:

net stop readyboost
net stop slsvc
net start slsvc
net start readyboost
@cls

Save the file as something.bat

This will stop ReadyBoost first (which depends on SLSvc), then SLSvc, then restarts both in opposite order, then it will close the command window. It needs to be run as administrator. If you need to work with the Notification service, too, for some reason, just add net stop/start SLUINotify in the appropriate places.

Thanks, man--you know you're the man, right?
thanks agian.

 

[eastwald]

I know this is an old thread - but just wanted to thank Maxxify - I keep VM's of all prior operating systems (I've got a few clients still using Vista) and ran into this same problem. Your solution worked like a charm. Can't say thanks enough.