Hi All,

I have Wsus 3.2, and there is 1 update that wsus cant download it completely.

i get error massage at Event Viewer - "Content file download failed. Reason: CRC verification failure. Source File: /msdownload/update/software/svpk/2011/10/visiowwsp3_1448da24c14974c0fde36f0667e05a0d54f6d552.cab Destination File: d:\WSUS\WsusContent\52\1448DA24C14974C0FDE36F0667E05A0D54F6D552.cab"

How Can i identify update name using this name "1448DA24C14974C0FDE36F0667E05A0D54F6D552.cab"

to cancel it? 

Thanks.

Hello All,

All of a sudden i am getting this error on all the clients. I have a internal wsus server, which my clients will connect and get the updates. Its working till Dec 3rd, i didnt made any changes.. but it stopped working.

Please help me

2015-01-05    18:54:13:281    1064    ae8    AU    Triggering AU detection through DetectNow API
2015-01-05    18:54:13:281    1064    ae8    AU    Triggering Online detection (interactive)
2015-01-05    18:54:13:281    1064    15f4    AU    #############
2015-01-05    18:54:13:281    1064    15f4    AU    ## START ##  AU: Search for updates
2015-01-05    18:54:13:281    1064    15f4    AU    #########
2015-01-05    18:54:13:283    1064    15f4    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:54:13:283    1064    1430    Agent    *************
2015-01-05    18:54:13:283    1064    1430    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-01-05    18:54:13:283    1064    1430    Agent    *********
2015-01-05    18:54:13:283    1064    1430    Agent      * Online = Yes; Ignore download priority = No
2015-01-05    18:54:13:283    1064    1430    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-01-05    18:54:13:283    1064    1430    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-01-05    18:54:13:283    1064    1430    Agent      * Search Scope = {Machine}
2015-01-05    18:54:13:283    1064    1430    Setup    Checking for agent SelfUpdate
2015-01-05    18:54:13:284    1064    1430    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
2015-01-05    18:55:24:178    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2015-01-05    18:55:24:186    1064    1430    Misc     Microsoft signed: Yes
2015-01-05    18:55:24:257    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2015-01-05    18:55:24:261    1064    1430    Misc     Microsoft signed: Yes
2015-01-05    18:55:24:297    1064    1430    Setup    Determining whether a new setup handler needs to be downloaded
2015-01-05    18:55:24:297    1064    1430    Setup    SelfUpdate handler is not found.  It will be downloaded
2015-01-05    18:55:24:297    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:299    1064    1430    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:300    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:314    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:314    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:336    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:336    1064    1430    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
2015-01-05    18:55:25:375    1064    1430    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-01-05    18:55:25:375    1064    1430    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abcd.mydomain.com:8530/ClientWebService/client.asmx
2015-01-05    18:55:25:417    1064    1430    PT    WARNING: Cached cookie has expired or new PID is available
2015-01-05    18:55:25:417    1064    1430    PT    Initializing simple targeting cookie, clientId = a788c530-2b29-4113-81e6-381a1751ada9, target group = , DNS name = a12300.mydomain.com
2015-01-05    18:55:25:417    1064    1430    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SOAP Fault: 0x00012c
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     faultstring:Fault occurred
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ErrorCode:InvalidParameters(7)
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ID:fd13335d-34d0-49b6-b065-aefab8b836f8
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: PTError: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: Sync of Updates: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
2015-01-05    18:55:28:433    1064    1430    Agent      * WARNING: Exit code = 0x8024400D
2015-01-05    18:55:28:433    1064    1430    Agent    *********
2015-01-05    18:55:28:433    1064    1430    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-01-05    18:55:28:433    1064    1430    Agent    *************
2015-01-05    18:55:28:433    1064    1430    Agent    WARNING: WU client failed Searching for update with error 0x8024400d
2015-01-05    18:55:28:496    1064    15cc    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Search callback failed, result = 0x8024400D
2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Failed to find updates with error code 8024400D
2015-01-05    18:55:28:496    1064    15cc    AU    #########
2015-01-05    18:55:28:496    1064    15cc    AU    ##  END  ##  AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:55:28:496    1064    15cc    AU    #############
2015-01-05    18:55:28:498    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:28:500    1064    15cc    AU    AU setting next detection timeout to 2015-01-05 18:25:28
2015-01-05    18:55:28:500    1064    15cc    AU    Setting AU scheduled install time to 2015-01-06 05:30:00
2015-01-05    18:55:28:501    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:28:502    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:33:432    1064    1430    Report    REPORT EVENT: {633AB594-B0B7-426A-A49F-6F508897E1BA}    2015-01-05 18:55:28:433+0530    1   148    101    {00000000-0000-0000-0000-000000000000}    0    8024400d    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024400d.

I have just deployed WSUS 3.2 on Server 2012 R2. All my client computers are Server 2012 R2 as well. I configured all the settings via the default domain GPO to point to my WSUS server and when I check the reg settings on any of the clients I see all the settings I configured in the GPO are being pushed down. But when I go to the All Computers in the WSUS console there are no clients showing up. At first I thought it had to do with the port number not being in the Specify Intranet Microsoft update service location all I had was the server name. I then changed it to 'servername:8530' and that change got pushed down but still no clients show up in the Computer's section in the WSUS admin console.

Is there something I should check or may be missing here?

Thanks

I setup a new WSUS server and then changed name of old one to something else and then renamed new one what the old one was. None of the clients are connecting to new WSUS server even though the GPO should be pointing to correct name. Is there something else I have to do in order for PCs to sync now?

Thanks

Arora,Jitender

Hello. I have seen many posts and discussions on clients showing as not reporting yet in the wsus server. I have built the WSUS server role and i have gotten 6 computers to show was installed and receive updates from the wsus. I am having issues having the other server to report.

1) have set up a GPO pushed to all the servers, yet only the one server continues to show as not reported yet.

2) i have taken it off the domain and readded it to the domain with no success.

3) have did the wsus update diagnostic tool

4) have did the wuauclt /detectnow; wuauclt /resetauthorization; wuauclt /report commands all to no avail.

Any help would be greatly appreciated. I have also tried to install the KB updates seen on the other posts: KB2959977, KB2720211 neither have worked.

Been at it for a couple weeks to no avail. HELP!!!!!!!!!!!!!!!Clients not reporting in

I've recently built a Windows 2012 R2 server with SQL Express advanced 2008 and WSUS. Im trying to export the approval database to import in to a non internet system. Every time I run wsusmigrationexport I get the following error:

WsusMigrationExport failed with the below exception!
System.BadImageFormatException: Could not load file or assembly 'Microsoft.UpdateServices.Utils, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
File name: 'Microsoft.UpdateServices.Utils, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
   at Microsoft.WsusMigrationTools.ExportServerStatus.DumpData(XmlTextWriter dataWriter)
   at Microsoft.WsusMigrationTools.WsusMigrationTool.Main(String[] args)

=== Pre-bind state information ===
LOG: User = INTERNET-WSUS\Administrator
LOG: DisplayName = Microsoft.UpdateServices.Utils, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 (Fully-specified)
LOG: Appbase = file:///C:/Program Files (x86)/Update Services 3.0 API Samples and Tools/WsusMigrate/
LOG: Initial PrivatePath = NULL
Calling assembly : Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.
LOG: Post-policy reference: Microsoft.UpdateServices.Utils, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35
LOG: Attempting download of new URL file:///C:/Program Files (x86)/Update Services 3.0 API Samples and Tools/WsusMigrate/Microsoft.UpdateServices.Utils.DLL.
ERR: Failed to complete setup of assembly (hr = 0x8013101b). Probing terminated.

Can anyone please help?

I am trying to get to the bottom of a version question.

We currently have SCCM 2012 R2 up and running, with a DB on a separate server version MSQL 2008 R2. Now we also are using the WSUS integration. I am being told WSUS 4.0 cannot be ran on SQL server 2008 R2, so they could only install and use WSUS version 3.0.

Can anyone out there please shed some light on my version items from above?

Thank you

If I install Windows Software Update Services I noticed that the Windows Internal Database gets automatically selected. If I am planning on installing\pointing the DB on a remote SQL server can I uncheck the Windows Internal Database feature without causing any problems with application?

Thank you

WSUS is not fully working

I find the below alerts in Operation manager

Application Pool worker process is unresponsive

The description for Event ID ( 2147488659 ) in Source ( Microsoft-Windows-WAS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
WsusPool, 12148, -.

Application Pool worker process terminated unexpectedly

The description for Event ID ( 2147488657 ) in Source ( Microsoft-Windows-WAS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
WsusPool, 11248, e0434f4d.

In the System log I find the warning

The Pool is running and I have already tried recycling the pools.

The description for Event ID 5013 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

WsusPool

11756

In the Application log I find

Warning

Event code: 3001

Event message: The request has been aborted.

Event time: 1/7/2015 4:32:58 PM

Event time (UTC): 1/7/2015 10:32:58 PM

Event ID: 2dc2f9ad3b3a46c8937aad1700efddae

Event sequence: 328

Event occurrence: 1

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/1205299030/ROOT/ClientWebService-2-130651434398492491

    Trust level: Full

    Application Virtual Path: /ClientWebService

    Application Path: C:\Program Files\Update Services\WebServices\ClientWebService\

    Machine name: server

Process information:

    Process ID: 11620

    Process name: w3wp.exe

    Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:

    Exception type: HttpException

    Exception message: Request timed out.

Request information:

    Request URL: http://serverad.domain.edu:8530/ClientWebService/client.asmx

    Request path: /ClientWebService/client.asmx

    User host address: x.x.x.x

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:

    Thread ID: 11

    Thread account name: NT AUTHORITY\NETWORK SERVICE

    Is impersonating: False

    Stack trace:

 Custom event details:

And error

An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/1205299030/ROOT/ClientWebService

Process ID: 11620

Exception: System.InvalidOperationException

Message: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

StackTrace:    at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)

   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect()

   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)

   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler)

   at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes)

   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetConfiguration()

   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()

   at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)

   at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)

   at Microsoft.UpdateServices.Internal.DataAccessCache.DeploymentChange(Object byTimer)

   at System.Threading.ExecutionContext.runTryCode(Object userData)

   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading._TimerCallback.PerformTimerCallback(Object state)

Any idea as to what is going on?

We have a small maintenance Windows to install Windows Updates on many servers.

It is very time consuming to have to manually access each server via Remote Desktop, click on the GUI and wait for updates to slowly install and then go back to them when the machines are ready for the restart to reboot them.

We can't use WSUS deadlines either because we would have to go back to the WSUS console and remove the deadlines after the maintenance Window is over to make sure that there are no unexpected reboots in the future (when new servers are added that are missing updates that have deadlines in the past) and that would be very labor intensive and time consuming.

Is there a command line that we can either manually run remotely or else set as a scheduled task that would initiate the  installation of updates 20 minutes before the maintenance window starts, but not do any automatic rebooting?

This would save us a ton of time because at the maintenance Window comes, all we would need to do is initiate the restarts remotely using "shutdown -I" for groups of servers that can be offline at the same time (all domain controllers cannot restart at the same time, VM hosts cannot all restart at the same time and VM hosts and VM guests cannot restart at the same time etc.).  Once a group servers are back online, we could do the same for the next group of computers until they are all done.

If we didn't have to Remote Desktop into each server and manually start the updates and then wait around for the updates to install before rebooting, it would probably cut down the amount of time it takes to install updates by two thirds.

Recently, Microsoft has identified a possible issue with WSUS server and Windows update clients.
These issues would occur and reflect in event logs with following event ID:
Event ID: 16
In the WindowsUpdate.log you may see the following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
While going through event logs under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational you may find an error event ID: 25 as follows
===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 25
Task Category: Windows Update Agent
Level: Error
Keywords: Failure, Check for Updates
User: SYSTEM
Computer: <computer name>
Description: Windows Update failed to check for updates with error 0x800b0001.
======================================

Cause:

This can be due to a version mismatch between the Windows update agent and the WSUS server. WSUS needs to be at version 3.2.7600.251 or later in order to properly communicate with clients at version 7.6.7600.256 or later.

Resolution:
Meanwhile to resolve this issue, one of the most workable troubleshooting steps listed as follows:

NOTE:
However please make sure that the issue that you try to resolve should have error 0x800b0001 and event ID 25 as shown above.
Troubleshooting steps:
1. Check windowsupdate.log in order to understand what is causing this issue.
2. If you find following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
(To understand how to access and read the Windowsupdate.log file please refer to following link –
http://support.microsoft.com/kb/902093 )
Follow the steps:
3. Stop the Automatic Update service or run command: “net stop wuauserv”.
4. Open Regedit and browse to the following Registry Key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
5. Save a copy of this WindowsUpdate key (File / Export or Right-click / Export).
6. Delete the following registry values:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDo
mainSid.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId
7. Close Regedit.
8. Start the Automatic Update service or run command: “net start wuauserv”.
9. On client machine, force synchronization with the WSUS Server: “wuauclt /detectnow”.
10. Now check windows update and click “Check for new updates”.
11. If a message with green bar appears indicates that issue is resolved.
12. If a message with red bar appears indicates that issue is not resolved and proceed with
further troubleshooting.
13. In command prompt run the command: “netsh winhttp show proxy” – and check for
any proxy configuration. If proxy is not configured proceed as follows.
14. Stop WIN HTTP Proxy service and windows update service and registered important
DLLs required for the changes to take place.
net stop WinHttpAutoProxySvc
net stop wuauserv
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s.
15. In windows registry, for following Registry Key - take a backup: "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate."
16. Delete the following registry value.
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId”
17. Run iisreset command in command prompt to restart all IIS related services and start windows update service.
18. On the client, do force synchronization with the WSUS Server by running command: “wuauclt /detectnow”.
19. After conducting the troubleshooting steps, we checked the event logs and found following success event on the client machine under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational:

===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 30
Task Category: Windows Update Agent
Level: Information
Keywords: Connection
User: SYSTEM
Computer: <computer name>
Description: Windows Update established connectivity.
===================================

Hence this issue is resolved. No further action is required.
20. If this event is not found proceed further with following steps:
21. Open "notepad"
22. Copy the following commands and then paste them into the opened Notepad window: net stop wuauserv net stop CryptSvc ren %windir%\system32\catroot2 catroot2.old ren %windir%\SoftwareDistribution sold.old net start CryptSvc net start wuauserv pause
23. We are renaming two files by this - catroot2 and SoftwareDistribution.
24. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
25. Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
26. You will see a DOS-like window processing. Now try Windows Update to see if the issue has been resolved.
27. If your issue is not resolved again then apply following update on the WSUS server machine Please be sure apply this update to WSUS SERVER MACHINE

http://support.microsoft.com/kb/2734608

28. Apply this update. 29. You must restart the computer after you apply this update.
30. Start synchronization on WSUS
31. Wait for the synchronization to succeed.
32. On the affected client, open cmd.exe in elevated mode
33. Type the following commands. Make sure that you press Enter after you type each command: Net stop wuauserv Net start wuauserv
34. The issue would be resolved once and for all.

 Microsoft has released this update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2)

 This update strengthens the WSUS communication channels.

 The Windows Update Agent (WUA) on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update.

 WSUS must be in a known, good working state for this update to work. If WSUS is configured to synchronize updates from Microsoft Update, make sure that WSUS can synchronize updates. And, clients must be able to communicate with the WSUS server.

 This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

Any improvements or feedback on above troubleshooting steps is surely welcome.
Thank You.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Security Update for Microsoft .NET Framework keep failing to install.Found teh following updates not getting installed ...

Any workaround for this issues

Hi everyone,

I'm trying to find what is the latest supported version of MSSQL 2012 and it seems only SP1 is supported if I follow the documentation bellow:

http://technet.microsoft.com/en-us/library/hh852344.aspx

Can anyone confirm if SP2 is supported or not?

Many thanks,

WSUS was working

All computers are reporting as they should.

No computers have updated since 12/10

WSUS services have been restarted, server cleanup has been run. Nothing in the logs is clearly indicating what went wrong.

Help!

In Sequence of Windows update installation, my module is calling WUA API IUpdateDownloader::BeginDownload to download update.

It's working properly and installation also completes successfully for admin kind of System user but it's getting fail in case of OS standard user.

Issue: When I logged-in with Windows standard user (on XP 64-bit) and tries to run my module, it's getting failed on BeginDownload call and returned with error code 0x80240044.

There is one failure entry under WindowsUpdate.log as well like:

WARNING: WU client fails CClientCallRecorder::BeginDownloadUpdates2 with error 0x80240044

Under link, I came to know that 0x80240044 stands for WU_E_PER_MACHINE_UPDATE_ACCESS_DENIED,which directly says that issue is specific to limited access permission to logged-in user.

Here, my query is :

Can we update client machine with standard user profile or not?

Can we provide only such type of permission programmatically that standard user can perform Windows update install operations?

Please let me know if someone knows solution for same.

Thanks in advance...:)

We have this setup and sort of working. However, when I say sort of, basically we have to give the machine\computer name account (domain.com\xxxxx$) that WSUS is running on sysadmin role privs on the DB instance that resides on the remote SQL server. This is unacceptable and I cannot locate any other documentation explicitly stating what role(s) are needed on the SQL server DB for WSUS.

Has anyone else ran into this? Thank you.