Hi there
we are using Windows Server 2008 on the upstream and Downstream WSUS.
We having an issue on this month . one of our downstream was unable to download the patch even i try to get from MS or upstream, on the event view , i got many error 364 .
Content file download failed. Reason: File cert verification failure. all 40GB patch seem Downloaded over and over again.
Please advise any check we can see.
thank you
After I enroll my device to mdm service, I check the updates by mdm command, then I get the update guids from device.
I sync these updates info from wsus based on this article https://docs.microsoft.com/en-us/windows/client-management/mdm/device-update-management, then I get some updates info, but not all of them. Some updates return 500 Internal Server Error for sws.update.microsoft.com/v6/ServerSyncWebService/serversyncwebservice.asmx. Guid for example 662b9834-63fe-43cd-b57b-8ea62da33001.
But it is reported by device , it seems to be a driver update.
It seems that I can not sync any driver update info from sws.update.microsoft.com.Neither can I get it from Microsoft Update Catalog, so where can I get these updates info by the guid reports from device?
Thanks!
Hi, I'm have installed WSUS on server 2019 and everything seems to be running fine, except I'm getting a warning "Feature Unavailable" The Microsoft Report Viewer 2012 Redistributable is required for this feature.
I have installed ReportBuilder, ReportViewer and SQLSysCLrTypes as suggesting in a solution to get WSUS Working on server 2016, but on server 2019 the message keeps popping up.
Has anybody got it working on server 2019?
I wanted to try out a test 2019 WSUS server. Everything seemed to go smoothly, however when I go look at All Computers, I get a system node crash.
I looked at the possibility of it being the same as the bad BIOS name, but I do not seem to see any errors.
The error is as follows:
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\. System.InvalidCastException -- Unable to cast object of type 'System.Guid' to type 'System.String'. Source Microsoft.UpdateServices.BaseApi Stack Trace: at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchComputers(String computerTargetScopeXml) at Microsoft.UpdateServices.Internal.BaseApi.ComputerTarget.SearchComputerTargets(ComputerTargetScope searchScope, UpdateServer updateServer) at Microsoft.UpdateServices.UI.AdminApiAccess.ComputerTargetManager.GetComputerTargets(ComputerTargetScope searchScope) at Microsoft.UpdateServices.UI.AdminApiAccess.BulkComputerPropertiesCache.GetAndCacheComputers(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope) at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()
Has anyone come across this error before?
Thanks.
Hello Microsoft Community,
I'm trying to figure out what is happening with the WSUS server so far no success
WSUS is trying to download 287gb of updates.. how?
Most of my clients are WIN10(1809 with july commulative updates)
1x WIN8.1 and 2x WIN7
I'm downloading the updates only with 2 languages and with the next product classifications:
also:
Can't uncheck the UPGRADES part, it is always coming back after unchecking it...
I don't have Automatic Approvals rules
Dont have downstream serversWhat steps I need to perform to eliminate this errors?
I have only 1 Wsus installed
I'm new to WSUS, try to explain it to me the easy way please.
Hello,
I am trying to install updates ( tried also manually after downloading it) on the server and the update gets stuck.
CBS log gets stuck at :
2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-KpsServer-servercommon-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-KpsServer-servercommon-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed Invalid 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerDatacenterCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerDatacenterCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerDatacenterEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerDatacenterEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Staged 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerDatacenterEvalCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerDatacenterEvalCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerDatacenterEvalEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerDatacenterEvalEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerStandardCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerStandardCorEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent 2019-07-22 17:19:50, Info CBS Appl: detect Parent, Package: Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, Parent: Microsoft-Windows-ServerStandardEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present 2019-07-22 17:19:50, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerStandardEdition~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed 2019-07-22 17:19:50, Info CBS Appl: Evaluating package applicability for package Package_5732_for_KB4471321~31bf3856ad364e35~amd64~~10.0.1.5, applicable state: Installed Invalid 2019-07-22 17:19:50, Info CBS Unexpected: Source State: Staged, Target State: Installed Invalid 2019-07-22 17:19:50, Info CBS ASSERT: Assertion failed in onecore\base\cbs\core\cbsexecutionitem.cpp(108) Unable to match state from StateToAction table
Do you have any hints what to search for?
Kind regards,
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.
I'm having problems with WSUS downloads at almost every client site this month that has Windows 10 1809 and Windows Server 2016 or 2018. The updates are downloaded but all show as "Not Applicable" or "No Status." Updates for Windows 7 and Windows 2008/2012 are OK.
Has something changed that would cause this issue? I haven't changed any group policy settings or anything else regarding WSUS at these sites. All of these WSUS installations have been working fine for months and in some cases years.
TIA,
Deb
Deb
Hi all,
I've got about 200 clients configured to use one of our WSUS servers - this has been up and running for at least a year and has been mostly OK.
However, there are a few computers (about 15-20) that suddenly aren't installing the latest 2019-07 updates even though they are showing as Pending within WSUS and on the client itself. Windows Update on the clients show the update as Pending, with an Install Now button
On the majority of our clients normal reboots will install updates, without the user ever having to do anything manually so i don;t know why i've suddenly got this issue.
All clients are using the same GPO with the latest ADMX files etc. and there is nothing that i can see that is different about them than any other client that is installing the update automatically. I know i can deadline the updates to (probably) force the issue, but i've never needed to do this before.
Please could you anyone let me know if they have any ideas?
My WSUS server lost its mind and revealed 6000+ old updates that need to be addressed. These go back to 2011. I've pruned the list down to just 166 updates.
I'd like to just decline all updates prior to 2019. There are dozens which apply to my 2008 servers.
I'm afraid that approving these very old updates (3+ years old) will have an adverse impact on my servers which are running just fine right now.
Can anyone suggest whether I should just blindly decline these old updates and only focus on the 2019 patches?
hello friends,
in wsus console root update services i have the download status that goes in loop.
The download goes to 644,xxx.yy and then return to 642.xxx.yy.
Do you have any suggestions to solve the problem?
Many thanks
Hi All,
i have setup a WSUS server and everything is find except that the client computers did not report to the server. I have configured a GPO already based on what i saw and read from the forums and youtube. What would be missing?
Any idea would be great!
Thank you very much and more power.
Hi There,
Thanks!
Scott
SuperSquatch
I run WSUS on a Server 2016 Essentials box (meaning the same box is also a DC and DNS server).
Desktops in the small environment are using WSUS to get updates. However the WSUS server itself, and another Server 2016 in the environment, are sometimes reaching out directly to Windows Update, bypassing WSUS. For example, KB4509475, released two days ago, hasn't even shown up in WSUS yet but it is awaiting install on two servers. Also, sometimes the servers show a "Last Contact" of the previous day, like they don't check in as often as the desktops.
Why are the servers bypassing WSUS?
More details to follow.
Mark Berry
MCB Systems
Hi, I'm using PowerShell and would like to query my WSUS server which is using WID database.
I connected to DB with this commands
[void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
$wsus=[Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer("WSUSSERVER",$false,"8530")
$db = $wsus.GetDatabaseConfiguration().CreateConnection()
$db.connect()
And what now ? How can I now query the DB ?
Please if you could provide an example how to do that - let's say an example how to get something fromvUpdate VIEW.
Thank you.
Windows clients are reporting to WSUS but not offering any patches for clients, but some of the clients are getting updates successfully.Tried with all the troubleshooting steps but no luck.
WSUS server installed on windows 2016 standard, clients are windows 10 and latest build version 1803,1809 and 1903 versions
Dear Community Members,
I'm hoping someone can steer me in the right direction with a problem I have with MS Endpoint Protection Definitions (KB2461484) not being installed when presented through WSUS.
The deployment has been working fine for several months and stopped on 9th July for all workstations. Other updates seem to be unaffected as many have been installed after this date.
The WSUS server is running on Windows 2012 R2 and the clients receiving the MS Endpoint Protection Definitions are Windows 7 machines. There is a GPO in place which configures the Endpoint client to check for definition updates every 2hrs. The WSUS server has been configured with an automatic approval policy to approve all ‘Definition Updates’ for ‘System Centre Endpoint Protection’ which is working fine since the update is set to ‘Install’ for all computers.
The updates can be seen downloaded on WSUS and initially the status remains as ‘No Status’ but once the clients begin detecting the status changes to ‘Installed/Not Applicable’. The update is definitely not installed as the client shows an old definition and nothing is shown in the Windows Update history.
Communication is fine between the clients and WSUS server and the excerpt below shows the Windows Update log from the client machine. I have deleted the SoftwareDistribution folder and ran wuauclt /resetauthorization, wuauclt /reportnow, wuauclt /detectnow all to no avail. I have also run the WSUS Server Cleanup Wizard and re-indexed the WSUS DB all to no avail.
Can anyone suggest anything to resolve this issue?
================
Windows Update Log
================
2019-07-25 12:28:30:779 1572 69c COMAPI -------------
2019-07-25 12:28:30:779 1572 69c COMAPI -- START -- COMAPI: Search [ClientId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:30:779 1572 69c COMAPI ---------
2019-07-25 12:28:30:779 1572 69c COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:30:779 1004 758 Agent *************
2019-07-25 12:28:30:779 1004 758 Agent ** START ** Agent: Finding updates [CallerId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:30:779 1004 758 Agent *********
2019-07-25 12:28:30:779 1004 758 Agent * Online = Yes; Ignore download priority = No
2019-07-25 12:28:30:779 1004 758 Agent * Criteria = "(IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains 'a38c835c-2950-4e87-86cc-6911a52c34a3' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b')"
2019-07-25 12:28:30:779 1004 758 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019-07-25 12:28:30:779 1004 758 Agent * Search Scope = {Machine}
2019-07-25 12:28:30:935 1004 758 PT +++++++++++ PT: Starting category scan +++++++++++
2019-07-25 12:28:30:935 1004 758 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS:8530/ClientWebService/client.asmx
2019-07-25 12:28:31:326 1004 758 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2019-07-25 12:28:31:326 1004 758 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS:8530/ClientWebService/client.asmx
2019-07-25 12:28:31:419 1004 758 Agent * Found 0 updates and 4 categories in search; evaluated appl. rules of 11 out of 13 deployed entities
2019-07-25 12:28:31:950 1004 758 Agent *********
2019-07-25 12:28:31:950 1004 758 Agent ** END ** Agent: Finding updates [CallerId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:31:950 1004 758 Agent *************
2019-07-25 12:28:31:950 1572 e18 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:31:950 1572 e18 COMAPI - Updates found = 0
2019-07-25 12:28:31:950 1572 e18 COMAPI ---------
2019-07-25 12:28:31:950 1572 e18 COMAPI -- END -- COMAPI: Search [ClientId = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)]
2019-07-25 12:28:31:950 1572 e18 COMAPI -------------
2019-07-25 12:28:36:960 1004 758 Report REPORT EVENT: {77AC4476-2CD7-4602-9721-E5875C73FAC7} 2019-07-25 12:28:31:950+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 Microsoft Forefront Endpoint PrSuccessSoftware Synchronization Windows Update Client successfully detected 0 updates.
Hi,
Ive had this issue with June & Julys Cumulitive Update for Windows 10 1809 x64-Base Systems. They keep on failing to install. I was scratching my head with the June release but evejtually declined that as July's release came out and hoping it would work but failed.
Any ideas what could be causing this?
Ive tried to delete the SoftwareDist folder, verified the files in WSUSContent, chkdsk and also dism.exe /scanhealth all with no luck.
Many Thanks,
Brad