Hi,
I notice on our WSUS servers that number shown on the Needed Count column for an update is always quite a bit higher than the value shown when you hover the mouse over the status icon.
For instance I'm seeing 944 in the Needed count column for an update, status icon shows "This update is needed by 611 computers".
Is this behavior normal and if so which count is the more reliable?
Thanks
I have a Server 2016 with WSUS Role installed. I have approved the feature Upgrade to Windows 10 1903 for a test group. The Upgrade downloaded to WSUS just fine and the upgrade downloaded to the Client without issue. The user selected the Upgrade Tonight option vs Schedule (wish I knew what upgrade tonight even means) and the Computer shows it is pending a Restart in the Windows Update settings Dialog. WSUS shows a status of Installation successful and restart required for the following update: Feature update to Windows 10 (business editions), version 1903, en-us x64. We left the machine overnight and it did not Upgrade or at least look like it attempted to upgrade (Does the machine just prompt the user at night?). Is there away to automate the installation of the upgrade without interaction by the users? Our PC's are authorized to install updates on there own every night at 7:00 pm however upgrades don't seem to respond to this authorization. Is there away to force the Install at a specific time without the user interacting with the upgrade? I really want all of the machines approved for upgrades to install at night to prevent someones machine from getting high jacked by the upgrade when they need to use it. Any guidance would be great.
Thanks.
Hi,
Are Windows_2012 DC and WSUS fully compatible with Windows_10 updates or better to upgrade WSUS Server to Windows_2016 or 2019?
Thanks.
I have good number of Windows 10 1903 clients trying to run windows update. They can get everything I've approved in WSUS except for the Servicing Stack Update for Windows 10 Version 1903 for x64-based Systems. Each time it stalls at "Downloading - 0%". Every client, Every time.
So, I'm thinking there's something going on with my WSUS box.
The only work around is going to each box and installing the update manually that I get from Windows Catalog.
Any ideas?
TIA. -Michael.
Hi all,
We have some Win10 kit on 1709 professional and enterprise. We use WSUS interally and have not approved any verison upgrades, but these machines have started trying to upgrade to 1809.
The issue is we don't want these machine to update versions but we do want to install patches for their current version.
How do we totally prevent them from updating because right now it looks like they will update at some point in the future.
Thanks
Hi All,
i need to get update release notification from from microsoft. i configured update notification from WSUS server but i need to
get notification from from microsoft.
please help me to sort it.
Thanks.
Hello,
I have several questions related to using WSUS behavior -
Superseding patches:
1. If a patch X is supreseded by patch Y and I install it - would it automatically remove patch X? Do I even need to remove it, what's the best practice for that?
2. Is there any way to retrieve a list of all superseeded patches in the system? (not GUI)
Patch Prerequisites:
3. Are there any general prerequisites that I need before installing patches on my servers?
Patch Dependencies:
4. How do I know if there are dependencies between patches (for example patch A needs to be installed before patch B)? If I install patch B, would it automatically install patch A eventhough I'm not aware of that? Is there an matadata on patch dependencies I can get from the patch itself ?
Thanks in advance,
Gili
I have a Windows Server 2012 R2 box that I am trying to install WSUS on but during post deployment it is failing with the following error:
2017-08-31 14:44:09 CreateDefaultSubscription failed.
Exception: System.Web.Services.Protocols.SoapException:
System.Web.Services.Protocols.SoapException: Server was unable to process request.
---> System.TypeInitializationException: The type initializer for
'Microsoft.UpdateServices.Internal.ApiRemoting' threw an exception. --->
System.UnauthorizedAccessException: Access to the path 'Update Services' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory
(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at System.IO.Directory.CreateDirectory(String path) at
Microsoft.UpdateServices.Log.GetUsableLogFileName
(String fileName, LogFileLocation& actualLogLocation) at
Microsoft.UpdateServices.Log.InitializeFromConfig() at
Microsoft.UpdateServices.Log.InitializeIfNeeded() at
Microsoft.UpdateServices.Internal.ApiRemoting..cctor()
--- End of inner exception stack trace --- at
Microsoft.UpdateServices.Internal.ApiRemoting..ctor()
--- End of inner exception stack trace --- at
Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow
(SoapException soapException) at
Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer
(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2017-08-31 14:44:09 StartServer encountered errors.
Exception=System.Web.Services.Protocols.SoapException: Server was unable to process request.
---> System.TypeInitializationException: The type initializer for
'Microsoft.UpdateServices.Internal.ApiRemoting' threw an exception. --->
System.UnauthorizedAccessException: Access to the path 'Update Services' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at
System.IO.Directory.InternalCreateDirectory(String fullPath, String path,
Object dirSecurityObj, Boolean checkHost) at
System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at System.IO.Directory.CreateDirectory(String path) at
Microsoft.UpdateServices.Log.GetUsableLogFileName
(String fileName, LogFileLocation& actualLogLocation)
at Microsoft.UpdateServices.Log.InitializeFromConfig()
at Microsoft.UpdateServices.Log.InitializeIfNeeded()
at Microsoft.UpdateServices.Internal.ApiRemoting..cctor()
--- End of inner exception stack trace --- at
Microsoft.UpdateServices.Internal.ApiRemoting..ctor()
--- End of inner exception stack trace ---2017-08-31 14:44:09
Microsoft.UpdateServices.Administration.CommandException:
Failed to start and configure the WSUS service at
Microsoft.UpdateServices.Administration.PostInstall.Run() at
Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
We have installed all the latest windows updates on this server and tried to rerun post deployment and it still fails with the same error.
We have other servers with WSUS running perfectly fine so I compared the permissions on the actual folder 'Update Services' under C:\Program Files\Update Services against a SBS server and made sure they are the same, issue still occurs.
Could someone please assist regarding this on what we can check further to get this working on this machine.
I.T. Construct admin@itconstruct.com.au http://itconstruct.com.au
Hello,
After applying KB4494440 which is the May CU update I started receiving the following error when manually checking for windows updates:
"We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you are connected to the internet."
It has also broken a PowerShell script I have to check for pending updates on servers as well utilizing Microsoft.Update.Session. I receive the HRESULT code: 0x8024402C when running the script, but no error code in the Windows UI. This has also affected my Windows 10 machines as well in the same manner after applying the May CU for Windows 10. If I uninstall the update the issue goes away. I have also tried the June CU that just came out yesterday and it has the same behavior.
Environment:
Offline network with WSUS on Server 2012R2
Server 2016 1607
Service Stack Update KB4498947 is applied
Patches are applied up to 04/2019
All other OS's in the environment are still functioning properly
Has anyone else seen this or have any suggestions as to how to resolve this?
Thanks
Dears
My windows 7 Machines not showing in WSUS (windows 2016).
Error showing in Logs --> "Windows Update Client failed to detect with error 0x80072ee6"
I tried all below but still same problem.
1. I recreated the Software Distribution Folder and also remove the registry values same error as mentioned above.
2. I run the SFC and DISM tools to fix the issue but same error.
3. Below also working fine.
Try to download the WSUS iuident CAB file from the client machine.
http://UpdateServerName:8530/selfupdate/iuident.cab
https://UpdateServerName:8531/selfupdate/iuident.cab
and then try to browse to:
http://UpdateServerName:8530/ClientWebService/client.asmx
https://UpdateServerName:8531/ClientWebService/client.asmx
4. Also check the ports and also in registry keys all fine.
5. I reinstall the update server also but no luck.
If anyone can help will be appriciated.
Thanks and Regards
Muhammad Faheem
Hi,
I have a wsus master running 3.0 SP2 (with KB2720211) running on 2003 Server R2 X64 which services about 40 downstream servers. 4 servers consistently are showing 0% in installed/not applicable. Please note that the master server was until recently a replica server. I had run the wsusmigration tool to copy from the old master server and checked settings were the same from the old master.
I have read many threads about similar issues that other people have had and this is what I have tried so far to no avail:
Uninstall wsus on downstream server and reinstalled
Uninstall iis and wsus on downstream server and reinstalled
Reset the pw on the anonymous IUSR_xxxxx account
Added the IUSR_XXX account to the security on \program files\selfupdate with read/execute etc
Uninstalled WSUS on the master server and reinstalled
Uninstalled report viewer and reinstalled on the master server.
Sync's from the downstream to the upstream say they have succeeded but I am seeing an error on the master server event viewer saying the report web service isn't working. This same error originally was coming up on the downstream server but after reinstalling wsus and iis that has gone. Now, all the other 30+ servers have %'s in that column but they don't seem to have changed much over the last few days. So, maybe they are bogus too. I can't figure out what else could be wrong so hoping someone here might have an answer. Thanks very much.
Hi,
After searching for some answers I found out that people with WS 2012r2 in order to view reports on WSUS install either Report Viewer 2008 SP1 Redistributableor MICROSOFT® REPORT VIEWER 2012 RUNTIME. I wonder in what situation would you choose either of them?
https://www.microsoft.com/en-ie/download/details.aspx?id=3841
https://www.microsoft.com/en-ie/download/details.aspx?id=6576
https://www.microsoft.com/en-IE/download/details.aspx?id=35747
There are already many articles on the net, but my thing is that Redistributable 2008 supposed to run only Windows Vista, Windows XP+.NET 3.5. Then 2008 SP1 Redistributable has Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP with .NET 3.5 SP1. Yet Only MICROSOFT® REPORT VIEWER 2012 RUNTIME supports the needed 2012 version (Windows 7, Windows 8, Windows 8.1, Windows Server 2003 Service Pack 2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Vista Service Pack 2).
MICROSOFT® REPORT VIEWER 2012 RUNTIME needs:
Hi everyone. I got problem with my wsus (win2012R2) wsus version 6.3.9600.18838 I noticed few days ago that when i click all computers in my wsus, console start crush and gets error node reset...
But when i use "search" .Then These computers are visible except one. When i serch for this one computer console always crush.
The problem is that i cannot remove this problematic computer from wsus because of crush. Any sugesstions?
How to solve this case? Or maybe a way to remove this computer from wsus DB ?
see please the screenshot...
the update shown as needing in WSUS. On pc it shows Successful. There are already few pcs in the same state.
33 machines are listed as needing. The computer park is 1000+ pcs. Most of them are correctly reported.
How to explain the inaccurate reporting? Just a bug? Or there is something known...
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Hi, does anyone know what SQL permissions are required to install this patch for WSUS to enable SHA 2 signing?
The SQL guys wont give me sysadmin to the instance hosting the SUSDB, so I need to know exactly wat permissions are required.
I thought that db_owner in the SUSDB would be enough, can anyone add to this please?
https://support.microsoft.com/en-gb/help/4484071/windows-server-update-services-update-kb4484071
doesnt say what permissions are required.
Thanks Tom.
Hi
I'm building a WSUS System environment on Windows 2019 Server.
My environment has an upstream and downstream-Server. The groupes are synced to the downstream server. As well the approved patches. Clients which are connected to the downstream server, get their patches correctly, as they are approved on the upstreamserver. I also see the correct status of the clients at the downstream-server.
But the status of the clients at the downstream-server are not synced back to the upstream-server.
How can I achieve, that i see all the client status (Updates needed, updates with error, etc.) on the Upstream-Server?
Thank you
Best regards
Martin
I have several clients I manage for Windows Updates using WSUS. The problem seems to be with Windows 10 workstations. Most of them are on v.1809. Now that Servicing Stack updates are downloaded along with other security updates, I've been approving them at the same time. My issue is that on many of my clients' Windows 10 1809 workstations, the servicing stack updates fail to install. The workstations get stuck downloading the update at 0% and then eventually it fails. At one client I checked recently, this happened on every single workstation with the current (May) updates.
I've Googled this issue but can't seem to find any relevant posts. I'd be glad to just stop approving them but I'm reading that eventually this could cause problems installing future regular updates. Any helpful advice would be appreciated.
Deb
Deb