Quantcast
Channel: WSUS forum
Viewing all 12874 articles
Browse latest View live

Is KB3046795 replaced by KB4338815 or KB4338824?

$
0
0

KB3046795 is a hotfix for solving W8.1 and WS12R2 reliability problems on skylake or kabylake processors, including only processor drivers (as shown in the file information section of KB3046795).

Recently, I noticed that the July cumulative update and the security-only update in order to enhance the security of AMD processors have refreshed the processor driver version. The MU Catalog does not mention whether KB4338815 and KB4338824 have replaced KB3046795.

I want to know if the processor driver in the July update includes the patching feature in the previous KB3046795.

 

This thread was originally posted here



Overcoming the slow WSUS Clean up

$
0
0

I was struggle for a little bit during the WSUS clean up process.  For me it timed-out every time.... I knew there were lots of updates that needed to be removed from the server.

Here is the PowerShell command I was running to do the clean-up:

Invoke-WsusServerCleanup -DeclineSupersededUpdates -DeclineExpiredUpdates -CleanupObsoleteUpdates -CleanupUnneed

For me the cause of the problem very slow SQL commands running in the WSUS database... which was the result of missing indexes. (By the way --- our WSUS server is running Windows Server 2016 with the latest patches, and the Database Engine is SQL Server 2016).

Before continuing.... please note that I have made changes to our WSUS database to increase performance.  No one else approved, acknowledged, or supported this.  If you decide to try this then you do so at your own risk...... a database backup is always a good thing.  (I know in my case, I will reverse the changes whenever I need to do a WSUS update, and then add them after the update completes.)

The command that stuck out like a sore thumb was "spDeleteUpdate".  It appears to execute once for each Windows Update, and it took over one minute to complete.  My first change was to add a clustered index to the temporary table in that stored procedure.  I changed this command: 

DECLARE @revisionList TABLE(RevisionID INT)
to this:
DECLARE @revisionList TABLE(RevisionID INT Index idx_nc_RevisionID CLUSTERED)

Just making this change improved the query execution.  What was talking555,000 reads was now only taking 2000.  The table "@revisionList" gets used in searches later in the stored procedure and the index makes it much faster.

Now comes the rest missing indexes which I applied directly to the tables.  I added quite of few.... and I realize some are probably not needed, but they certainly didn't hurt.  Here are the ones I added:

CREATE INDEX [IXMF_ivwApiUpdateRevision_IsLatestRevision] ON [SUSDB].[dbo].[ivwApiUpdateRevision] ([IsLatestRevision]) INCLUDE ([RevisionID], [IsHidden], [IsLocallyPublished], [IsMandatory]);
CREATE INDEX [IXMF_ivwApiUpdateRevision_IsLatestRevision_IsHidden] ON [SUSDB].[dbo].[ivwApiUpdateRevision] ([IsLatestRevision], [IsHidden]) INCLUDE ([LocalUpdateID], [EffectiveArrivalTime], [RevisionID]);
CREATE INDEX [IXMF_ivwApiUpdateRevision_UpdateID_IsLatestRevision_IsHidden] ON [SUSDB].[dbo].[ivwApiUpdateRevision] ([UpdateID], [IsLatestRevision], [IsHidden]);
CREATE INDEX [IXMF_tbDeadDeployment_TargetGroupID_TargetGroupTypeID_LastChangeNumber] ON [SUSDB].[dbo].[tbDeadDeployment] ([TargetGroupID], [TargetGroupTypeID],[LastChangeNumber]);
CREATE INDEX [IXMF_tbDeadDeployment_TargetGroupTypeID_LastChangeNumber] ON [SUSDB].[dbo].[tbDeadDeployment] ([TargetGroupTypeID], [LastChangeNumber]) INCLUDE ([DeploymentID], [RevisionID], [TargetGroupID], [UpdateID], [RevisionNumber]);
CREATE INDEX [IXMF_tbDeadDeployment_TargetGroupTypeID_LastChangeNumber_UpdateType] ON [SUSDB].[dbo].[tbDeadDeployment] ([TargetGroupTypeID],[LastChangeNumber], [UpdateType]) INCLUDE ([DeploymentID], [RevisionID], [TargetGroupID], [UpdateID], [RevisionNumber]);
CREATE INDEX [IXMF_tbDeadDeployment_TargetGroupTypeID_TimeOfDeath_ActionID] ON [SUSDB].[dbo].[tbDeadDeployment] ([TargetGroupTypeID],[TimeOfDeath], [ActionID]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbDeployment_ActionID_TargetGroupTypeID] ON [SUSDB].[dbo].[tbDeployment] ([ActionID], [TargetGroupTypeID]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbDeployment_DeploymentStatus_TargetGroupTypeID_LastChangeNumber_UpdateType] ON [SUSDB].[dbo].[tbDeployment] ([DeploymentStatus], [TargetGroupTypeID],[LastChangeNumber], [UpdateType]) INCLUDE ([GoLiveTime], [RevisionID], [TargetGroupID]);
CREATE INDEX [IXMF_tbDeployment_TargetGroupTypeID] ON [SUSDB].[dbo].[tbDeployment] ([TargetGroupTypeID]) INCLUDE ([ActionID], [RevisionID]);
CREATE INDEX [IXMF_tbDeployment_TargetGroupTypeID_ActionID] ON [SUSDB].[dbo].[tbDeployment] ([TargetGroupTypeID],[ActionID]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbDeployment_TargetGroupTypeID_LastChangeNumber] ON [SUSDB].[dbo].[tbDeployment] ([TargetGroupTypeID],[LastChangeNumber]) INCLUDE ([DeploymentID], [RevisionID]);
CREATE INDEX [IXMF_tbDeployment_TargetGroupTypeID_LastChangeNumber_UpdateType] ON [SUSDB].[dbo].[tbDeployment] ([TargetGroupTypeID],[LastChangeNumber], [UpdateType]) INCLUDE ([DeploymentID], [DeploymentStatus], [ActionID], [GoLiveTime], [Deadline], [DownloadPriority], [IsAssigned], [RevisionID], [TargetGroupID], [IsLeaf], [Priority], [IsFeatured], [AutoSelect], [AutoDownload], [SupersedenceBehavior]);
CREATE INDEX [IXMF_tbDeployment_TargetGroupTypeID_UpdateType_LastChangeNumber] ON [SUSDB].[dbo].[tbDeployment] ([TargetGroupTypeID], [UpdateType],[LastChangeNumber]) INCLUDE ([DeploymentID], [ActionID], [Deadline], [RevisionID], [TargetGroupID], [Priority]);
CREATE INDEX [IXMF_tbEventInstance_EventNamespaceID_TimeAtServer] ON [SUSDB].[dbo].[tbEventInstance] ([EventNamespaceID],[TimeAtServer]) INCLUDE ([EventOrdinalNumber]);
CREATE INDEX [IXMF_tbFileOnServer_ActualState] ON [SUSDB].[dbo].[tbFileOnServer] ([ActualState]) INCLUDE ([FileDigest], [RowID], [TimeAddedToQueue]);
CREATE INDEX [IXMF_tbLocalizedPropertyForRevision_LocalizedPropertyID] ON [SUSDB].[dbo].[tbLocalizedPropertyForRevision] ([LocalizedPropertyID]);
CREATE INDEX [IXMF_tbProperty_CreationDate_ReceivedFromCreatorService] ON [SUSDB].[dbo].[tbProperty] ([CreationDate], [ReceivedFromCreatorService]) INCLUDE ([RevisionID], [PublicationState]);
CREATE INDEX [IXMF_tbProperty_ExplicitlyDeployable_UpdateType] ON [SUSDB].[dbo].[tbProperty] ([ExplicitlyDeployable],[UpdateType]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbProperty_PublicationState] ON [SUSDB].[dbo].[tbProperty] ([PublicationState]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbProperty_PublicationState_ReceivedFromCreatorService] ON [SUSDB].[dbo].[tbProperty] ([PublicationState],[ReceivedFromCreatorService]) INCLUDE ([RevisionID], [ExplicitlyDeployable], [UpdateType]);
CREATE INDEX [IXMF_tbRevision_IsLatestRevision] ON [SUSDB].[dbo].[tbRevision] ([IsLatestRevision]) INCLUDE ([RevisionID], [LocalUpdateID]);
CREATE INDEX [IXMF_tbRevision_IsLeaf] ON [SUSDB].[dbo].[tbRevision] ([IsLeaf]) INCLUDE ([RevisionID], [LocalUpdateID]);
CREATE INDEX [IXMF_tbRevision_IsMandatory] ON [SUSDB].[dbo].[tbRevision] ([IsMandatory]) INCLUDE ([LocalUpdateID], [RevisionID]);
CREATE INDEX [IXMF_tbRevision_State] ON [SUSDB].[dbo].[tbRevision] ([State]) INCLUDE ([LocalUpdateID], [RevisionID]);
CREATE INDEX [IXMF_tbRevisionInCategory_CategoryID_Expanded] ON [SUSDB].[dbo].[tbRevisionInCategory] ([CategoryID], [Expanded]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbRevisionInCategory_Expanded] ON [SUSDB].[dbo].[tbRevisionInCategory] ([Expanded]) INCLUDE ([RevisionID], [CategoryID]);
CREATE INDEX [IXMF_tbRevisionSupersedesUpdate_SupersededUpdateID] ON [SUSDB].[dbo].[tbRevisionSupersedesUpdate] ([SupersededUpdateID]);
CREATE INDEX [IXMF_tbUpdate_IsHidden] ON [SUSDB].[dbo].[tbUpdate] ([IsHidden]) INCLUDE ([LocalUpdateID], [UpdateID]);
CREATE INDEX [IXMF_tbUpdate_IsHidden_ImportedTime] ON [SUSDB].[dbo].[tbUpdate] ([IsHidden],[ImportedTime]) INCLUDE ([LocalUpdateID], [UpdateID]);
CREATE INDEX [IXMF_ivwApiUpdateRevision_IsLatestRevision_IsHidden_IsLocallyPublished] ON [SUSDB].[dbo].[ivwApiUpdateRevision] ([IsLatestRevision], [IsHidden], [IsLocallyPublished]);
CREATE INDEX [IXMF_tbDeployment_UpdateType_LastChangeNumber] ON [SUSDB].[dbo].[tbDeployment] ([UpdateType],[LastChangeNumber]) INCLUDE ([RevisionID]);
CREATE INDEX [IXMF_tbFileOnServer_ActualState_DSSRequestedDownload] ON [SUSDB].[dbo].[tbFileOnServer] ([ActualState], [DSSRequestedDownload]) INCLUDE ([FileDigest], [RowID]);
CREATE INDEX [IXMF_tbFileOnServer_DSSRequestedDownload] ON [SUSDB].[dbo].[tbFileOnServer] ([DSSRequestedDownload]) INCLUDE ([FileDigest]);

Note:  If you are running these in SQLCMD, make sure you run "set quoted_identifier on" first. 

The end result: What took over a minute to execute "spDeleteUpdate" now takes a small fraction of the time.  The entire clean-up command completed successfully in a reasonable amount of time, and I got about 60 GB of disk space back.

Hope this helps someone who has ran into a same problem.


How to configure wsus clients

$
0
0
I installed wsus on a 2003 r2 server that is in a workgroup instead of an AD. The clients windows 7 and windows 10 I would like to configure them to connect to the server wsus. The url that shows me the installation of wsus is http: // myserver / selfupdate
I do not know if I should configure in the registry or by gpo in the clients and where exactly.

Also, how can I check that my wsus is working correctly?
Thank you.

Issues with KB4338819, video drivers failing to start?

$
0
0

Hey guys!

I'm in the middle of deploying updates, and while deploying the 2018-07 Cumulative Update for Windows 10 Version 1803 to my test group, I've noticed a pretty severe bug. It seems that after the computer restarts, the video drivers fail to launch properly? This results in the monitors and computer behaving as if it is asleep, but it's unable to be awoken by typical keystrokes. It requires the user to specifically hit the key combination Ctl_Shift_Win_B to restart their video drivers. let's chase this bug down! Is this an issue with the graphics driver, or just a symptom of another problem being resolved by the restart of said driver?

Any input would be appreciated! (even if it's moving this post to the right place! ha!)

Thanks for your time.

Whats difference in Windows 10 Products WSUS?

$
0
0

In our enviroment we are rolling out Windows 10 Pro and I'm configuring WSUS to update those Windows 10 clients.

In the products categorie there are a lot Windows 10 options but what is the difference?
- Windows 10 and later drivers
- Windows 10 and later upgrade & Servicing drivers
- Windows 10 Feature On Demand
- Windows 10 GDR-DU
- Windows 10 Language Interface Packs
- Windows 10 Language Packs
- Windows 10 LTSB
- Windows 10

Also in the Classifications you can choose between "Update Rollups", "Updates" and "Upgrades". What is the difference and what I need to take?

Thanks in advance.

Consuming too much virtual memory

$
0
0

I have a WSUS with WID installed.  I installed the SQL Management Studio.  I set the Min memory to 2 GB and the Max memory setting to 6GB.  The OS (Windows Server 2012R2) has 15GB physical memory installed and the paging file can use up to 24 GB.  The WSUS downstream to me cannot synchronize with me and my server is failing to synchronize with the upstream source.  The error message I receive is "out of memory" essentially.  The connection between my WSUS console the database keeps dropping frequently.  I look at Task Manager Details pane and the SQLserver process is using almost all the virtual memory on the box.  No matter what I do nothing seem to correct the problem.

How can I prevent the WID from consuming all the virtual memory?  Should I just give up and install SQL Express?

WSUS 6.3 Console Always Crashed with Error ID:7053

$
0
0

Enviroment: Windows Server 2012 R2 + WSUS6.3 + Domain

I build the WSUS Roles on windows server 2012 r2 with WID database,If not client connected everything is ok,But if many clients connect this server,when i click the Computers Groups on the WSUS Console,the Console will crashed show  error:Unexpected Error and evnet log haderror id :7053

 ,I had rebuild the windows and wsus roles for 3 times,the is the same error.

Now i have no idea,Is there anybody can help me to fix this issue ?

There is error log :

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\.


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.Xml.XmlException -- '', hexadecimal value 0x18, is an invalid character. Line 1, position 1159930.

Source
System.Xml

Stack Trace:
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
   at System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType)
   at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
   at System.Xml.XmlTextReaderImpl.ParseText()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlReader.ReadStartElement()
   at System.Xml.Serialization.XmlSerializationReader.ReadStringValue()
   at System.Xml.Serialization.XmlSerializationReader.ReadTypedPrimitive(XmlQualifiedName type, Boolean elementCanBeType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read1_Object(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read2_GenericReadableRow(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read339_Item()
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
** this exception was nested inside of the following exception **


System.InvalidOperationException -- There is an error in XML document (1, 1159930).

Source
System.Xml

Stack Trace:
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchComputers(String computerTargetScopeXml)
   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()


WSUS - The Reporting Web Service is not working.

$
0
0

Hello guys, I have a VM with RRAS and  WSUS installed.

VM has two NICs, one for RRAS and the other one for WSUS.

WSUS does not seem to display computers, it has this error: The Reporting Web Service is not working.

When I type netstat -ano | find "8530"

I'm able to see clients establishing connection to WSUS server. But unable to see on WSUS homepage.

WSUS need to be on a stand alone server? or what?

Please help. Thanks.


Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.


The WSUS administration console was unable to connect to the WSUS Server via the remote API. (kb3159706)

$
0
0

My WSUS stop working when I installed kb3159706 and ran the post install so I can deploy Windows 10 Anniversary Update. Has anyone ran into this same problem? Below is my log. 

The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

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.IO.IOException -- The handshake failed due to an unexpected packet format.

Source
System

Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **


System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

Escalating a bad patch issue

$
0
0

Post from the BizTalk Server forum: https://social.msdn.microsoft.com/Forums/en-US/2d08c395-1550-4171-8c03-23e1d2a9afbc/an-internal-failure-occurred-for-unknown-reasons-winmgmt?forum=biztalkgeneral

A recent set of patches appear to be making the BizTalk Administration components and BAM components to error fatally.  It seems to be any patch related to the following CVEs:

e.g. KB4338419, KB4338605, KB4338424, KB4338825

What's the best way of getting this escalated within Microsoft?


If this is helpful oranswers your question - please mark accordingly.
Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
Read my articles on: BizTalk |.NET

WSUS shows wrong Windows 10 Version after Update KB4338819

$
0
0

Hello,

after the update KB4338819 to the Windows 10 Clients WinVer Shows version 1803 (Build 17134.165).
On the command promt (cmd.exe) the Version is: [Version 10.0.17134.165].

But on the WSUS Server the clients show  10.0.17134.137.

Is this only on my Wsus Server so (Windows Server 2012 R2)?

Thanks
Bruno



Many Clients Not yet report

$
0
0

Hi

I have a WSUS server 2012 R2: 6.3.9600.18838, I've done a .bat to make the clients to connect to my server, after the .bat, the client contact the server, but it don't report, the .bat I've done with many links in the web:

@echo on
net stop wuauserv
net stop bits
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIdValidation /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /d 0 /f /t REG_DWORD
rd /s /q "C:\WINDOWS\SoftwareDistribution"
ren c:\windows\WindowsUpdate.log c:\windows\WindowsUpdate.old
net start bits
net start wuauserv
wuauclt /a /resetauthorization /detectnow
WUAUCLT /r  /reportnow

Well, the rename for WindowsUpdate.log does not work...

I'm worried because I don't know what is wrong, in the WSUS console, appear the machine but with "Last Status Report" like "Not yet report".
This is the "WindowsUpdate.log" after running the .bat:

2018-07-08 12:00:52:550  564 a28 AU ###########  AU: Uninitializing Automatic Updates  ###########
2018-07-08 12:00:54:235  564 a28 Service *********
2018-07-08 12:00:54:235  564 a28 Service **  END  **  Service: Service exit [Exit code = 0x240001]
2018-07-08 12:00:54:235  564 a28 Service *************
2018-07-08 12:01:00:257  564 1018 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: -0500)  ===========
2018-07-08 12:01:00:257  564 1018 Misc   = Process: C:\Windows\system32\svchost.exe
2018-07-08 12:01:00:257  564 1018 Misc   = Module: c:\windows\system32\wuaueng.dll
2018-07-08 12:01:00:257  564 1018 Service *************
2018-07-08 12:01:00:257  564 1018 Service ** START **  Service: Service startup
2018-07-08 12:01:00:257  564 1018 Service *********
2018-07-08 12:01:00:257  564 1018 Agent   * WU client version 7.6.7601.24085
2018-07-08 12:01:00:257  564 1018 Agent   * Base directory: C:\Windows\SoftwareDistribution
2018-07-08 12:01:00:257  564 1018 Agent   * Access type: No proxy
2018-07-08 12:01:00:257  564 1018 Agent   * Network state: Connected
2018-07-08 12:01:01:926  564 1018 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2018-07-08 12:01:01:941  564 1018 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2018-07-08 12:01:01:988  564 1018 Agent WARNING: Failed to read the service id for re-registration 0x80070002
2018-07-08 12:01:01:988  564 1018 Agent WARNING: Missing service entry in the backup data store; cleaning up
2018-07-08 12:01:02:409  564 113c Report CWERReporter::Init succeeded
2018-07-08 12:01:02:409  564 113c Agent ***********  Agent: Initializing Windows Update Agent  ***********
2018-07-08 12:01:02:409  564 113c Agent   * Prerequisite roots succeeded.
2018-07-08 12:01:02:409  564 113c Agent ***********  Agent: Initializing global settings cache  ***********
2018-07-08 12:01:02:409  564 113c Agent   * WSUS server:http://VMMXWSUSM.asl.local:8530
2018-07-08 12:01:02:409  564 113c Agent   * WSUS status server:http://VMMXWSUSM.asl.local:8530
2018-07-08 12:01:02:409  564 113c Agent   * Target group: Va
2018-07-08 12:01:02:409  564 113c Agent   * Windows Update access disabled: No
2018-07-08 12:01:02:409  564 113c DnldMgr Download manager restoring 0 downloads
2018-07-08 12:01:02:409  564 1018 Agent Created new random SusClientId c79f58cf-ecfe-4b4f-85ad-ba8244042d5a. Old Id: none.
2018-07-08 12:01:02:409  564 1018 Report ***********  Report: Initializing static reporting data  ***********
2018-07-08 12:01:02:409  564 1018 Report   * OS Version = 6.1.7601.1.0.65792
2018-07-08 12:01:02:409  564 1018 Report   * OS Product Type = 0x00000030
2018-07-08 12:01:02:534  564 1018 Report   * Computer Brand = VMware, Inc.
2018-07-08 12:01:02:534  564 1018 Report   * Computer Model = VMware Virtual Platform
2018-07-08 12:01:02:550  564 1018 Report   * Bios Revision = 6.00
2018-07-08 12:01:02:550  564 1018 Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0    
2018-07-08 12:01:02:550  564 1018 Report   * Bios Release Date = 2014-04-14T00:00:00
2018-07-08 12:01:02:550  564 1018 Report   * Locale ID = 1033
2018-07-08 12:01:46:995  564 1018 AU ###########  AU: Initializing Automatic Updates  ###########
2018-07-08 12:01:46:995  564 1018 AU   # WSUS server:http://VMMXWSUSM.asl.local:8530
2018-07-08 12:01:46:995  564 1018 AU   # Detection frequency: 6
2018-07-08 12:01:46:995  564 1018 AU   # Target group: Va
2018-07-08 12:01:46:995  564 1018 AU   # Approval type: Scheduled (User preference)
2018-07-08 12:01:46:995  564 1018 AU   # Scheduled install day/time: Every day at 3:00
2018-07-08 12:01:46:995  564 1018 AU   # Auto-install minor updates: Yes (Policy)
2018-07-08 12:01:46:995  564 1018 AU Setting AU scheduled install time to 2018-07-09 08:00:00
2018-07-08 12:01:46:995  564 1018 AU Successfully wrote event for AU health state:0
2018-07-08 12:01:46:995  564 1018 AU Initializing featured updates
2018-07-08 12:01:46:995  564 1018 AU Found 0 cached featured updates
2018-07-08 12:01:46:995  564 1018 AU Successfully wrote event for AU health state:0
2018-07-08 12:01:46:995  564 1018 AU Successfully wrote event for AU health state:0
2018-07-08 12:01:46:995  564 1018 AU AU finished delayed initialization


I've installed "HTTP Activation" in the server manager for .NET Framework 4.5 and 3.5 in the WSUS Server

So I have some questions:
1.- Why the .bat don't rename the WindowsUpdate.log?
2.- Did I missed a KB for the WSUS? because I couldn't find a place that shows me the neccesaries KB for WSUS 2012 R2
3.- What else can I do?
In Advanced thank you.


Héctor Ponce TechNet

Windows 10 Pro for Workstations - Not-Applicable (WSUS) for 1803 Feature Update

$
0
0

We've been battling an issue at our organization for several months now regarding Windows 10 Professional 1709 workstations not receiving the 1803 Feature Update that was released in early May 2018.  The main symptom of this issue is that these workstations are showing a status of "Not Applicable" for the 1803 Feature Update which has applied for other workstations.


We have identified that the only workstations exhibiting this behavior show an operating system name of "Windows 10 Pro for Workstations", as opposed to the other workstations' OS (which received 1803 through WSUS successfully) simply named "Windows 10 Pro".  


Is there a separate set of instructions for servicing feature updates to Windows 10 Pro for Workstations through WSUS that we are missing?  These machines are receiving all other dynamic and cumulative updates without issue through WSUS, it is only the 1803 Feature Update that will not recognize as "needed".


Thank you,


Solved, Cured, Fixed - Windows Update Error 0x80244019

$
0
0

In the past several months I have upgraded WSUS on a Server 2012 Standard installation, and did a clean install of WSUS on the same. For both, the final WSUS version was 6.2.9200.17646  The issue on both was the same. Windows 7 computers were seen by WSUS, but the status never changed from "not yet reported". After days of trying to figure it out and following numerous and countless so-called solutions I found on the Internet – and not just on Microsoft support sites, it became apparent that even Microsoft was clueless as to the true *root cause* of the problem, and while many of the so-called solutions offered were just patches, not fixes. I realized I was just another guinea pig in their fruitless and unsuccessful attempts to find that root cause. It got to the point where I just gave up and using group policy set up all Windows 7 computers to get their updates directly from Microsoft.

When dealing with a large number of Windows 7 machines, getting updates directly from Microsoft would really tie up bandwidth every Monday during the day, since many of the machines are turned off over the weekend and holidays. The slowdowns weren’t only noticeable; they made the network overall excruciatingly slow for the entire day. When users would reboot their computers thinking that would solve their problem, the entire update process for that computer would just start over, adding to the time the available bandwidth was maxed out. The buffer bloat on the Internet modem contributed even more to the bandwidth issue.  So with the onset of the new year and the fact that business was slowing down for me, I decided to tackle this issue and actually "solve" it….not "patch" it. I succeeded.

First, I found a client with a perfectly working WSUS version 6.2 on Server 2012 Standard and began looking for differences. Of course, I found lots of them. It took me over two weeks to find the difference that solved the problem once and for all.  It seems that on the working WSUS, it had three file directories with files, that neither of the non-working WSUS setups had. To test this, I temporarily removed these three directory paths and their contents from the working WSUS, and found that I was getting the same exact error as on the non-working setups.

On the non-working setups, reviewing the windowsupdate.log file on the windows 7 computers, they all had the same error.

WARNING: WU client failed Searching for update with error 0x80244019
>>##  RESUMED  ## AU: Search for updates [CallId = {C70DBC7D-66FD-40B0-AB20-0A9E9EF92081}]
# WARNING: Search callback failed, result = 0x80244019
# WARNING: Failed to find updates with error code 80244019

While the Callid GUID may be different, the error 0x80244019 was consistent. Understand that this is but one of hundreds of issues that can generate this same exact error. If it were up to me, the description for error 0x80244019 would be "We haven’t got a clue!"  Yet upon adding the missing directories and their subsequent files, everything cleared up and has worked perfectly since.  So here’s what you need to to.

First, stop the WSUS Service. From an elevated command prompt enter

Net stop WSUSService

Now ensure the three following paths exist, assuming you installed WSUS to it’s default location.

C:\Program Files\Update Services\SelfUpdate\WSUS3\ia64\win7sp1

C:\Program Files\Update Services\SelfUpdate\WSUS3\x64\win7sp1

C:\Program Files\Update Services\SelfUpdate\WSUS3\x86\win7sp1

If necessary, create the win7sp1 directory in each of the three directory paths, if it doesn’t already exist. Then copy the following files from the exact source directory indicated, to the exact destination directory indicated.

For 64-bit Windows 7

Copy the contents of C:\Windows\WinSxS\amd64_updateservices-selfupdate-x64-win7sp1_31bf3856ad364e35_6.2.9200.17025_none_ae5ccf24bda5b809 to C:\Program Files\Update Services\SelfUpdate\WSUS3\x64\win7sp1

Note that it may be necessary to create the win7sp1 subdirectory.

For 32-bit Windows 7

Copy the contents of C:\Windows\WinSxS\amd64_updateservices-selfupdate-x86-win7sp1_31bf3856ad364e35_6.2.9200.17025_none_1043c229991acc59 to C:\Program Files\Update Services\SelfUpdate\WSUS3\x86\win7sp1

Note that it may be necessary to create the win7sp1 subdirectory.

For Itanium based (IA64) Windows 7

Copy the contents of C:\Windows\WinSxS\amd64_updateservices-selfupdate-ia64-win7sp1_31bf3856ad364e35_6.2.9200.17025_none_84d35a4d6a8284f3 to C:\Program Files\Update Services\SelfUpdate\WSUS3\ia64\win7sp1

Note that it may be necessary to create the win7sp1 subdirectory.

When done, from an elevated command prompt restart the WSUS service.

Net start wsusservice

Then restart all the Windows 7 computers and in about a hour they will have all "checked in" with WSUS and will be getting updates.

I still can’t comprehend why the many versions of the windows update diagnosis program that many have downloaded, don’t check for accessibility to that win7sp1 directory along with the other directories for other versions of windows, and simply report that it’s inaccessible or non-existent on the WSUS server. For a so-called diagnosis program, it appears to not be a very good one, since it doesn’t diagnose something as elementary as the existence of a required path and file, and report that to the user in plain English if it’s the problem.  Even further, it would appear that the routines which install the WSUS role on the server is not all inclusive of what needs to be installed and present for a fully functional WSUS. So it is of my unprofessional and uneducated opinion that Microsoft needs to fix the problem at the role installation source. Maybe then, they can do away with wasting time on a program to diagnose it, since it would appear to not diagnose this specific issue anyway. I'm done ranting. Thanks for reading. I feel better now. :)

WSUS takes long to Synchronize

$
0
0

Hello,

Am installing WSUS on a Win server 2012. We only accept 1 languages.

on Synchronizing, takes long time and no error displays or does not stop!!.

Thanks in advance.


WSUS editions

$
0
0

Hi

I'm wondering wich edition of WSUS use:

  • Windows 2008 R2
  • Windows 2012 R2
  • Windows 2016

This is because when I used WSUS of Windows 2008 R2, aparently I had no problems, but with Windows 2012 R2 at the beginnig all worked very well, but around 2 monts later the clients began to have problems to reporting and get updates.

2016 I haven't used.

The kind of clients are Windows 7 to Windows 10 any versions.

So, should I have to work with 2008R2 is better than 2012 R2?

What could be your advice?


Héctor Ponce TechNet

PC directly connect to Internet to update not via WSUS after upgrading to 1709

$
0
0

Hi All,

Once the PC was upgraded from 1511 to 1709, it seems that GPO didn't work very well.

There is a "Allow connecting to Windows Update locations" which was conflict with the other one "Do not connect to any windows update  internet  locations".    The "allow connecting to windows update lcoations"  is not in our group policy.  Wonder where it is coming from?  Is there anyone who can explain it? Thanks!


How do I determine where a computer got the 1709 feature upgrade?

$
0
0

Hi Folks,

TL;DR: How can I tell where a Win10 Enterprise machine got a feature upgrade from after the feature upgrade has been performed?

I've been tasked with getting a hold of Windows Updates at our org. I had a 2016 server stood up with WSUS and attached 3 laptops (w/ 1511, 1607, and 1703 images on them) to it to confirm my understanding of the settings that arbitrate WUA behavior. On this development WSUS server all feature upgrades are denied. Those three laptops sat in my office for 2 months and everything seem to be operating as intended until one day the 1709 machine updated to 1709 one day.

The only GPO setting I have in place is the "Specify intranet Microsoft update service location" policy. AFAIK, nothing that enables dual scan should be in place, and I see nothing in gpresult /h or rsop.msc which indicates otherwise.

I'm aware of the Get-WindowsUpdateLog cmdlet and have used it to track what happened on a computer in the past but it only pulls from the online operating system. I tried pointing it at the .etl files in C:\Windows.old, but that didn't work.

Now I've been approached by a supervisor asking if we can cut over to my WSUS server and I am hesitant to do that for many reasons, chief among them the fact that a client still updated when it wasn't supposed to on my WSUS server.

Can anyone steer me in the right direction of finding out where/how that 1703 laptop got the 1709 feature upgrade?

Internal database error update sp4 win2003 r2 64bits

$
0
0
I installed wsus on a 2003 r2 64 bit server and installed sp2.Then I installed wsus and continued with windows update updating everything on the server, but I always get the error windows internal database sp4 (KB2463332) 0x80070643.

In the viewer I see:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11260
Date: 06/29/2018
Time: 7:59:44
User: FSERVER-MORA \ Administrator
Computer: FSERVER-MORA
Description:
The description for Event ID (11260) in Source (MsiInstaller) can not 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: Product: Windows Internal Database - Error 1260. Windows can not open this program because it has been prevented by a software restriction policy.For more information, open Event Viewer or contact your system administrator.
; (NULL); (NULL);(NULL); (NULL); ; .
Data:
0000: 7b 42 44 44 37 39 39 35 {BDD7995
0008: 37 2d 35 38 30 31 2d 34 7-5801-4
0010: 41 32 44 2d 42 30 39 45 A2D-B09E
0018: 2d 38 35 32 45 37 46 41 -852E7FA
0020: 36 34 44 30 31 7d 64D01}

And this other in the viewer system part:
Event Type: Error
Event Source: Windows Update Agent
Event Category: Installation
Event ID: 20
Date: 06/29/2018
Time: 7:59:54
User: N / A
Computer: FSERVER-MORA
Description:
Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Internal Database Service Pack 4 for x64 Edition (KB2463332).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 69 6e 33 32 48 52 65 Win32HRe
0008: 73 75 6c 74 3d 30 78 38 sult = 0x8

WUA API for /reportnow ?

$
0
0

We are controlling the behavior of the Automatic Updates service via the WUA COM API. The Automatic Updates service has been changed to Manual start, because our systems are embedded and we can only apply updates when the machine is in service mode.

At the end of service mode, our service reboots the machine to put it back into embedded/production mode, halting the Automatic Updates service. The problem I'm seeing is that the reports do not always get uploaded.

I noticed there is the wuauclt /reportnow option, but since it is asynchronous it would be hard to tell when the report upload has completed or failed. Is there an equivalent COM API?

 

Thanks in advance!

Viewing all 12874 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>