Archive for the ‘WindowsUpate’ Category

How to Fix RDP not Saving Password / Credentials (Windows Remote Desktop Connection)

Tuesday, November 12th, 2019

After upgrading to Windows 10, I have had some issues with a couple of RDP connections that wouldn’t store the username and password (credentials). Despite ticking the box to save the credentials, it would always prompt me to enter the password.

Here’s how to fix the issue with RDP not saving the login information, which should work not just on Windows 10, but also other versions of Windows if you have the same problem:

  1. Click Start and type “GPEDIT.MSC” to search for the shortcut to the Windows Group Policy Editor.
  2. Right-click the gpedit.msc shortcut and click run as Administrator.
    (Ignore any popups about errors if you get any when the Group Policy Editor console opens up).
  3. Browse to Local Computer Policy > Computer Configuration > Administrative Temples > System > Credentials Delegation
  4. Double click the setting called “Allow delegating default credentials with NTLM-only server authentication” to edit it.
  5. Change the setting to “Enabled” and then click the “Show…” button in the “Options:” window where it says “Add servers to the list:”.
  6. Double click the field below “Value” (with the black arrow to the left) and type in “TERMSRV/*” (without the double quotes).
  7. Click Ok and then Ok again to close both popups, so that you only see the list of settings again.
  8. Now just repeat the exact same for these three policies as well:
    Allow delegating default credentials
    Allow delegating saved credentials
    Allow delegating saved credentials with NTLM-only server authentication
  9. Close the Local Group Policy Editor and RDP should now work as expected again!
  10. Restart

How do I reset Windows Update components?

Saturday, October 24th, 2009


To reset the Windows Update components automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Note this Fix it Solution has two modes Default and Aggressive. You should run the Fix it solution in Default mode and determine if it resolves your problem with Windows Update before running it in Aggressive mode.

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)


Windows Update Not Working or Fails; Reset Windows Update Settings

Wednesday, November 19th, 2008

This is mostly seen with WSUS but I have run into it from time to time through regular day to day items.

While working on a server today I kept being informed that the Windows Updates were failing. When checking the Windows Update log file I found the error. From there I went about fixing it.

Turns out the junior guys were confused as I said “Ah.” and dropped to a command prompt. That reminded me that sometimes I really need to explain what is going on in my head to others.

This issue is really easy to fix. It usually happens when there is a problem with the installation of an update. In this case I found that the C: drive was in the middle of compressing files and it so happened that one of the folders was the “softwaredistribution” folder where updates are stored to be installed.

Here is what you need to do:

  1. Open a command prompt. (If you don’t know how please contact a technical support person)
  2. regsvr32 /u wuaueng.dll
  4. del C:\WINDOWSUPDATE.log (if this tells you that it is in use just go to the next step).
  5. Regsvr32 wuaueng.dll
  6. Net start wuauserv
  7. Wuauclt.exe /resetauthorization /detectnow

There you go, you should be able to request Windows Updates and they will download and install as you expect.

Svchost bruger muligvis 100% af cpu’en.

Monday, May 14th, 2007

I forbindelse med opdatering til v7 af Windowsupdate er der opst?et et problem p? rigtigt mange Win XP maskiner. Mange XP maskiner fors?ger at benytte den gamle v6 af websiten.

Symptomer: Kort efter at computeren er startet g?r den tilsyneladende kold i en lang periode. Svchost bruger muligvis 100% af cpu’en. Windows reagerer ikke p? h?jreklik og det er vanskeligt at f? task manager frem.

Start med at skrive services.msc, og stop dern?st servicen automatiske opdateringer. Det skulle give tid til at k?re nedenst?ende fixes.

Start med at opdatere Windowsupdate agenten. Det kan g?res ved at downloade den herfra:

Luk alle browsere mens opdateringen k?res.
Hvis der kommer en fejlbesked om at filen allerede er installeret, s? pr?v at installere den med wuforce switchen: WindowsUpdateAgent30-x86.exe /wuforce

K?r dern?st dette hotfix som l?ser et problem i msi.dll:

Hvis dette ikke l?ser problemet s? g?r f?lgende:
Stop automatiske opdateringer, men deaktiver ikke servicen.
G? til C:\WINDOWS\SoftwareDistribution\Download og slet indholdet af folderen. G? ogs? til C:\WINDOWS\SoftwareDistribution\DataStore og slet filen DataStore.edb (dette sletter windows update history).
Fors?g Windowsupdate.

Hvis det STADIG ikke virker, s? stands servicen automatiske opdateringer en gang til og omd?b SoftwareDistribution folderen til SoftwareDistribution.old. Windows skulle genopbygge den automatisk ved n?ste bes?g hos windowsupdate