We stop the Background Intelligent Transfer Service (BITS), and the Windows Update Service (wuauserv) services because we’re working with items that are in use by these services.Let’s walk through what is happening and why we’re doing it. This client-side script is something you should not be afraid of. Long Explanation: What is this Doing? Should I be Afraid of Running this? Normally it is noticeable within an hour, but sometimes it takes longer.
Wait 24-48 hours after running the client-side script above to see if the issues have gone away. Remove-Item "$env:SystemRoot\SoftwareDistribution\" -Recurse -Force -ErrorAction Silentl圜ontinue Remove-ItemProperty -Name AccountDomainSid, PingID, SusClientId, SusClientIDValidation -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\ -ErrorAction Silentl圜ontinue Remove the affected devices from the WSUS MMC console and then from an administrative PowerShell prompt on each affected system, run: Stop-Service -Name BITS, wuauserv -Force PowerShell.exe (New-Object -ComObject ).DetectNow() PowerShell Rd /s /q "%SystemRoot%\SoftwareDistribution" Reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f Reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f Reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f Reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f Remove the affected devices from the WSUS MMC console and then from an administrative command prompt on each affected system, run: net stop bits Quick Fix – Client-Side Script: Choose Your Method – Command Prompt, or PowerShell Command Prompt
0 kommentar(er)
