SLOW LOGIN — Setting up personalized settings for: Windows Desktop Update
I have an issue, whenever I log into an account its slightly delayed when going into the desktop environment and shows in the top left of the screen : Setting up personalized settings for: Windows Desktop Update and then takes about 4-5 minutes to log in while loading:
I would very much like to resolve the issue as it continues to pop up at all our site across the network.
They all use windows 7 and service pack 1 is installed
It happens to all users and administrators.
Please Help my poor IT mind 🙁
Replies (5)
As per the description, you are experiencing issue with slow login and it shows a screen on the top left: Setting up personalized settings for Windows desktop update and takes around 4-5 minutes to log in while loading on the system.
I certainly understand your concern.
I would suggest you to try following methods and check if it helps.
Method 1:
To diagnose the problem whether any third party program or application is causing the conflict, I would suggest you to try “clean boot” and check if it helps.
Placing your system in “Clean Boot” state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.
How to perform a “clean boot” in Windows, please follow the steps in the link provided below.
Important: Putting your system in Clean Boot state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.
Note : Refer «How to reset the computer to start normally after clean boot troubleshooting» to reset the computer to start as normal after troubleshooting.
Try to reboot the system and check if it helps.
If the issue persists, follow method 2
Method 2:
I would suggest you to try and follow the steps in the link given below and check if it helps.
How to use the System File Checker tool to repair missing or corrupted system files , please follow the steps in the link provided below.
Note: System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. This article describes how to run the System File Checker tool (SFC.exe) to scan your system files and to repair missing or corrupted system files in Windows. If a Windows Resource Protection (WRP) file is missing or is corrupted, Windows may not behave as expected.
Also, I would suggest to run system maintenance troubleshooter and check if it helps. Please follow the steps in the link given below.
Note: System maintenance troubleshooter looks for unused files and shortcuts that you clean up or remove so that your computer can run faster.
Open the System Maintenance troubleshooter.
You may also try to run a full computer scan with the Microsoft Safety Scanner to make sure that the computer is virus free.
Microsoft Safety Scanner, please follow the steps in the link provided below.
Note: Any data files that are infected may only be cleaned by deleting the file entirely, which means there is a potential for data loss.
I hope this information is helpful.
Please do let us know if you need any further assistance, we will be glad to assist you.
Personalized settings not responding after windows 10 updates
Windows 10 updates have been installed on a HP elitebook 8460p. When i reboot I am now stuck on the personalized settings not responding on a black screen. I have tried many things to no avail. The solutins that i have read have not been helpful. Any thoughts?
Replies (55)
* Please try a lower page number.
* Please enter only numbers.
* Please try a lower page number.
* Please enter only numbers.
This might be caused by corrupted system file. For us to provide a solution suitable to the not responding error, we need the following information:
- Which update was installed on your PC?
- Were there any other changes made to your device prior to the issue?
- Were there any error codes after you reboot the PC?
- What troubleshooting steps have you done so far?
In the meantime, try running the black screen troubleshooter as an initial workaround and see if it will help.
Looking forward to your response.
23 people were helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
In my case, this problem started after the Creators update.
I have a Dell Optiplex 760.
I have uninstalled my graphics drivers. No help.
I have unplugged all of my peripherals with the exception of the wireless keyboard and mouse. No help.
I have turned off fast boot or fast startup whatever it’s called. No help.
I removed my video card. No help.
Tried several other things I found online. Nothing has worked.
The only thing besides booting in safe mode that does anything is restoring a previous version of Windows. However, that is only a temporary fix as the Creators updates automatically downloads again and screws up my computer each and every time in a seemingly endless loop of frustration.
30 people were helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
Setting up personalized settings for windows desktop update
Question
I have created a package to deploy IE 10 in our environment. All works well as far as deployment goes. That is until a user with the command line restricted.
After IE10 is installed, a locked down user logs in and a window shows up titled «Personalized Settings»: Setting up personalized settings for: Internet Explorer A command line opens saying: The command prompt has been disabled by your administrator. Press any key to continue.
I would love to know what IE is doing and how to stop this message from happening for each locked down user. Thanks!
Answers
We have found that those registry keys in question did not resolve our problem. Our problem was still in ActiveSetup but the StubPath value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\
SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\
Where the executed command was:
C:\Windows\system32\cmd.exe /D /C start C:\Windows\system32\ie4uinit.exe –ClearIconCache
We found by deleting both of these keys IE works and the issue was resolved.
I believe I have fixed my issue.
There are 2 registry keys that are created by this command line.
HKCU\Software\Microsoft\Active Setup\Installed Components\
By deploying these keys via Group policy, the command line doesn’t run for the locked down users, and ie 10 works just fine. Frustrating, but it works.
All replies
How did you create the ie 10 package and deploy it to your environment?
Have you ever disabled the command prompt in Group Policy?
This policy prevents users from running the interactive command prompt, Cmd.exe. It also determines whether batch files (.cmd and .bat) can run on the computer.
(Note: Do not prevent the computer from running batch files if the computer uses logon, logoff, startup, or shutdown batch file scripts, or for users that use Terminal Services.)
Please go to Run -> type «gpedit.msc” -> User Configuration\Administrative Templates\System -> open «prevent access to the command prompt» -> select Disable or Not Configured.
We deployed the package via Configuration Manager 2012 as shown here:
using the command: ie10_package.exe /quiet /norestart /update-no
We have intentionally disabled the command line in our environment as we are a school district and don’t want students to have access to the command line.
We have previously updated from ie7 to ie8, and ie8 to ie9 without any issues or need for students to have access to the command line.
Since this issue only occurred in IE10, I’d like to know how did you deploy ie7, ie8 and ie9? Maybe something is different this time, as you described, the policy of “prevent access to the command prompt” is not the culprit, perhaps you can just disable it for a test.
Disabling the «Prevent access to the command prompt» does eliminate the cmd line opening with the message that «The command prompt has been disabled by your administrator.»
But then the user has access to the command prompt obviously. Not a viable option for us.
Previous deployments of IE7-9 were deployed as a software update using SCCM 2007. IE10 isn’t available in the same manner, so we used the recommended deployment method as stated, (http://technet.microsoft.com/en-us/library/jj822329.aspx)
Just to clarify. IE10 does deploy as it should. This message happens 1x on the machine for a locked down user. It has to do with updating their profile. After the locked down user logs in, closes out the failed command line window, they can then log out and back in that same machine without any message. The problem is that these locked down users use different computers every day. So unless they are logging into the same machine as they have after ie10 was deployed, they will get this command line window again. It’s an annoyance issue more than a functionality issue.