Search the Community

Hi all, Go and check your WSUS console. Its most likely broken or your client aren't receiving updates. I doscovered mine wasn't working after trying to do a forced update from a client to my WSUS server and it kept bugging out. If you dare, disconnect from the server in MMC and try to reconnect (at your peril) The error I was getting was "Cannot connect to server. SQL is not running." There is another post on here from @robsonma but I found a few more steps to get WSUS running after update KB3148812 breaks it. Read these: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/ https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ The fix: A manual operation... https://support.microsoft.com/en-us/kb/3159706 Worked for me. Hope this helps.

Who has the time to mess around every Patch Tuesday to review Microsoft's update releases? The most that I would really want out of WSUS is the ability to delay all updates by 2 weeks so when Microsoft releases a fatal upgrade wrecking millions of desktops, at least we won't get it until after the fallout and emergency revision is available. And it's not like WSUS is a very reliable release mechanism either. Does anyone recall the first release of Windows 7 SP1? The one that randomly killed large numbers of desktops? Windows 7 computer won’t start after installing Service Pack 1. - Microsoft Community I very nearly deployed that to an entire district overnight, but then thought eh, maybe I should wait. And then once the news hit about SP1 breaking machines, I was afraid to even attempt applying it. Ultimately I ended up deploying SP1 the old fashioned way, as a new image to each computer via WDS rather than risking using WSUS and breaking everything. So it became.... um..... why am I even bothering with WSUS? It just more make-work that doesn't really benefit me. And so WSUS went bye bye, and all machines in the domain are set to Automatic install all Windows and Microsoft updates. If Microsoft screws that up it's on their head, not mine.

Way before Christmas I re-installed WSUS on a 2008R2 DC. For a while it limped along until last week. Whenever I try to open WSUS via either Server Manager or Admin Tools or wherever else you can open it from, the snap-in fails to load and essentially MMC crashes. I do have a restart pending after some Windows Updates but unfortunately I'm only at this place once a week in the morning where they are heavily reliant on their server and network shared areas so I don't have the option to reboot when I am here. Are there any other things I can try before succumbing to telling them they NEED to reboot the server?

Hi All, After updating my internet connection I want to try downloading updates direct instead of WSUS - But still want to control them so we don't get versions (1903 for example) I found this box But you all know as well as I do how fragile WSUS is - Will this download the updates but only what's specified in WSUS, bypassing internal storage? I'm tired of it filling up so quickly. Cheers all,

Hi all! I've been tasked with checking up on our WSUS servers at our sites and was wondering; - When it comes to an update such as Cumulative Updates for .NET Framework 2022-08 which has been superseded by 2022-10 a. Do you still approve the 2022-08 update still or do you decline this b. What affect would declining this do? c. If I was to approve the older update, would machines with newer versions (2022-10) still try to pull the 2022-08 update? Any tips on WSUS in general would be greatly appreciated. The auto approval process is already set up, it's just updates like Edge and .NET / any other random unapproved updates that come through I'm struggling with.

Server info: OS Name: Microsoft Windows Server2019 Standard OS Version: 10.0.17763 N/A Build 17763 Original InstallDate: 1/17/2020, 12:25:18 PM Having issuesinstalling cumulative updates. It seems to have installed defender and .NETupdates fine. But can't get the current (Win 10 (1809) and Server 2019 -Cumulative Update (64-bit) January 10 2023) or previous December update toinstalled. If I try it manuallyit fails with MSI failed with error code -2146498304. When I try it fromWSUS or Microsoft it fails with 2023-01 Cumulative Update for Windows Server2019 for x64-based Systems (KB5022286) - Error 0x800f0900 I have tried toreset windows updates according to the below KB. https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/additional-resources-for-windows-update Ran the SFC /Scannowand the DISM restore health commands The restore health command fails withError: 0x800f0954 In Googling allthese error codes I'm basically chasing my tail. Everything keepscircling around to the same thing over and over and nothing seems to work, andeverything fails The below is from the windows update log. [font=Calibri]2023/01/1311:00:13.1374595 7128 8128 Handler CBS called Error with 0x800f0900, [/font] [font=Calibri]2023/01/1311:00:13.1402237 7128 8128 Handler CBS called Terminate[/font] [font=Calibri]2023/01/1311:00:53.9164837 7128 7556 Handler Completed install of CBS update withtype=0, requiresReboot=0, installerError=1, hr=0x800f0900[/font] [font=Calibri]2023/01/1311:00:54.0648649 7128 7556 Handler * END * CBS Install[/font] [font=Calibri]2023/01/1311:00:54.6929704 3664 5204 Agent *FAILED* [8024200B] Method failed[CAgentUpdateManager::InstallUpdate:11739][/font] [font=Calibri]2023/01/1311:00:54.8788666 3664 5204 Handler Loaded state: cCompleteIterations: 1,pt: SelfContainedNoExpressPayload, nNextRequestID: 1.[/font] [font=Calibri]2023/01/1311:00:54.9012256 3664 5204 Agent LogHistory called.idUpdate={447FF6C5-74A0-4DFD-A497-9039E898E010}.200, resultMapped=800F0900,resultUnMapped=800F0900[/font] [font=Calibri]2023/01/1311:00:54.9131342 3664 5204 Agent Install updates CallerId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9132320 2116 4776 ComApi Install ClientId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9140489 2116 4776 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font] [font=Calibri]2023/01/1311:00:54.9143000 2116 4776 ComApi Reboot required = False[/font] [font=Calibri]2023/01/1311:00:54.9143085 2116 4776 ComApi Exit code = 0x00000000; Call errorcode = 0x80240022[/font] [font=Calibri]2023/01/1311:00:54.9143100 2116 4776 ComApi * END * Install ClientId = UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9146923 3664 1652 Agent WU client calls back to install call{36B49B40-ED6B-4C7D-A74A-D2CC913B7D67} with code Call complete and error 0 [/font] [font=Calibri]2023/01/1311:00:54.9149632 2116 6932 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font]

Hi, I'm using the remote WSUS console from my computer on one subnet to connect to two different WSUS servers on two different subnets. I've managed to connect to one ok but the second one gives me the following error: Cannot connect to 'ServerName'. The server may be using another port or different Secure Sockets Layer setting. The WSUS server is running on port 80 and can connect to this via telnet so a little stumped as to why this isn't connecting. Connection traffic has been confirmed by the Firewall provider upstream so is getting through. Any ideas?

hi all our wsus 2008 server will not download the wsus updates, any ideas. Thanks

Hi, I'm not an idiot, and I've been working in IT for the part 12 Years, but I'm having a senior moment!. Can anyone tell me how to disable the restart computer notification for non-administrator on a 2k3 server. I'm using WSUS, and group policies are set to download updates, I log on and install them when I have a maintenance window, but the problem I have is that on the Terminal Server, all users get the restart computer notification, not just admins. non-admins don't have restart computer rights, so the only option they can click on is restart later. A few users find this very irratating, as the notification dialog takes the current window focus away from the app they were using. The only GP setting I can find is ' Allow non-administrators to recieve update notifications' which I have set to disabled. But they still recieve restart notifications. How do I turn this off?

Hi All, I'm now experiencing a very hard to understand situation, this is happening on my newly reinstall Windows Server 2003 R2 SP2 Standard on 32 bit platform. I've installed SP2 and IE 8 manually and then initiate the Windows Update from the website but it always failed, see the following attached log. I've activated this copy of Windows and also join this to the domain. any suggestion would be greatly appreciated. Thanks.

Hi All, I've got several hundreds of Windows Server 2003 and 2008 virtual machine + several physical machine which is updated by WSUS automatically but it needs to be restarted manually. Is there any way to know which server needs restart and which one is not ?( eg using powershell) Thanks

We have recently enabled and started using WSUS [updating station-by-station or at imaging time historically] It all looks very promising except for the fact that so few of my stations/laptops are showing up in Computers/All Computers [nearly half my computers are not shown!] I can't find any way to force a 'missing' station to appear in WSUS. Can anyone help? Server O/S: Windows 2003 Standard: SP2. Workstion/Laptop O/S: Windows XP Pro: SP 2 or SP3. XP Firewall is turned off by Group Policy. Thanks.

Hi Folks, Has anyone got experience of implementing WSUS on a Viglen Classlink system? Classlink Support say it can be done but it's not supported & I'd like to know if there are any issues. Regards RB

Hi I have just installed WSUS 3.0 on our Windows 2003 box, and the install has gone well, the server is available functioning and syncing quite happily with Microsoft Update. I have followed the deployment instructions by linking a new GPO object to the domain and have checked that the clients are receiving the correct GPO when logging on. If I check the local registry it tells me that the clients are pointed to our WSUS server to receive updates. However I cannot see any client computers in the WSUS computer group on the server, so it reports its got nothing to push the updates to. Thanks in advance Kevin

I did not set up our wsus server but it has been running just fine for several years until very recently. it was grabbing a bunch of updates and became stuck. i let it run for a while before canceling it out then applying the updates.. after it had installed updates the server needed rebooting which i did. server came back online just fine and all seemed good until i tried to load wsus. it seems to stick at loading, when you click on synchronization it stays at zero. after about 3 minutes, it will flash up a screen that it cannot connect to the wsus server, reset server node or copy to clipboard. i started the sql manager and can connect to the internal microsoft sql database.forgot to mention, this wsus in on this server computer.. all on same computer.

I've just setup my first WSUS server and I'm configuring a client workgroup to test everything is setup ok but I have a couple of questions and I would be greatful if anyone could fill me in about the recommended configuration. On the clients if I enable the 'Configure Automatic Updates' will the client still try to use Microsoft updates over the internet rather then our WSUS server? The description in GPO console makes it sound like it would. When clients attempt to connect to the WSUS server will the computer try to use the proxy settings defined as a few clients on our network still have the computer defined policy as our old and now removed cachepilot, an easy fix just changing this to our smoothwall but just checking as some on the server are having a few hundred updates as 'no status' Thanks

Morning All, I hope that someone might be able to help me with a really annoying issue. To cut a long story short, one of the techs often performs Windows Updates on non-domain computers using the school's internet connection (for exam computers, test machines, etc). When using the ISA server as the proxy on the client machine, it can take up to 10 minutes for updates to be detected. If using the upstream proxy server on the client machine the updates are detected almost straight away. Tried the following but still no joy: --------------------------------------------------------------------------- Tested updates from dc, removed dns forwarders and tested same result. Added opendns public dns server has forwarder and tested same result. Disabled AV on test server, same result. Added new update url to isa url set called "New Windows updates", created access rule from local host to the 2 update url sets and the one update domain set. Retested same result, deleted update IE object from browser and retested same result. --------------------------------------------------------------------------- I just cant work out why it takes soo long on non-domain computers. Has anyone encountered similar issue or know a resolution? Thanks guys.

Didn't know right section for this but as SC is based on Linux why not here i thought lol... Right we have just moved over the this system but i'm having great problems getting WSUS3 to update. The server it is running from has open access to the net without a username but when i try to synchronize or download the updates i get told that Now i've allowed the IP access and told it not to auth against windowsupdate.com but still nothing. Anyone else having problems. The funny thing is if i turn off the auth completely it works but no students can access the net.... Help

InfoWorld is reporting that on February 12th, Microsoft will roll out Internet Explorer 7 through Windows Server Update Services to all systems - regardless of whether or not the update had been requested previously. The piece also mentions ways to prevent the update from occurring, for sysadmins who do not want to use IE7 on their systems. Microsoft claims that the decision was made due to 'security concerns'.

Standing up a new MP/DP also making it a Software update point, on a server 2022 fully patched. When a new server comes out i try to make a MP/DP/SUP, for sccm just to get something new in there and make sure that works for a while, before standing up new one for the other boundary groups/ locations Like i have done in the past i install the feature and roles so that way when i add the server to sccm, those are already there. BITS differential compression Data deduplication ISAPI Extensions Windows Authentication IIS IIS 6 WMI Compatibility IIS 6 Metabase Compatibility Windows Server Update Services However even before its added to SCCM I'm having some trouble with WSUS. Below is the error i get when i launch WSUS to do the post install things. And yes i rebooted before launching the WSUS, and this is happening before i touches SCCM. Log file is located at C:\Users\USERNAME\AppData\Local\Temp\\WSUS_PostInstall_20211130T122430.log Post install is starting Fatal Error: The schema version of the database is from a newer version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database. When i look in the post install log the only error i can find is RAISERROR('Invalid schema version number', 16, 1) with nowait I have tried Removing the Wsus and deleting the database but when i do that i says Unable to open the physical file "C:\Windows\WID\Data\SUSDB.mdf" when i reinstall the wsus roles So i removed the server from SCCM the MP/DP was working fine btw, but since i felt like it screwed it up beyond repair i removed the roles and deleted the server from SCCM and deleted the VM. I'm now back to fully patched 2022 server. Before i start adding things i wanted to get your input as to what the issue could be with WSUS?