Quantcast
Channel: WSUS Forum
Viewing all 12331 articles
Browse latest View live

multiple .net updates failed

$
0
0

how to tackle this problem (screenshot below).

Couple of 2008 servers are in the same state...

As we can see only old .NET failed. Other updates are installed.

The server is managed by vendor.

I would like to see a clean installation history.

Even if these old .Nets are not necessary, how to clean this mess up.

Are they important from security point of view, if latest are installed?


--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis


error code 780

$
0
0
 keep receiving error code 780. online it said. window was unalbe to start SQL Server VSS writer services. right click on SQL Server VSS writer, and then click on properties. on the general tab, make sure the startup type isn set to automatic or manual.

Getting past WSUS Cleanup Wizard time out, removing unnecessary updates.

$
0
0

Standard problem with WSUS Cleanup Wizard timing out without removing any unnecessary updates. SBS2K8. WSUS 3. 6000+ unnecessary updates awaiting approval. Huge database. Unresponsive SQL server. Lot of people have this problem:
http://social.technet.microsoft.com/Forums/en-US/9724778f-c1a0-4d24-82e4-8b2d054257d6/wsus-hangs-on-cleanup-wizard-for-unused-updates-then-disconnects-from-console?forum=winserverwsus

Drives are regularly defragged in the background. Not gonna shut down the server and have down time just to fix this.

Tried the reindexing script from
http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx
, (don't copy the command line, it has weird characters in it, just type it in manually.) and it completes but it didn't improve anything.

Found this:
http://wsus.codeplex.com/releases/view/17612
and it also times out.

Found this comment:
For anyone who is getting Timeout Expired with obsolete updates. I have a solution! Use server name : "
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
" to connect with SQL managment studio. Once connected manually run "
exec spGetObsoleteUpdatesToCleanup
". This will return a list of obsolete ID's. For each one run "
exec spDeleteUpdate @localUpdateID=000000
", where 000000 is the ID. For myself I found the first ID in the list took a full 37 minutes to delete and then after that I could run the cleanup through the GUI as per usual.

by jjdacl on Apr 23 at 12:55 PM 

Found that you actually need to do:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup

And to connect in the first place, I had to hit Options, and select named pipe from the middle pull down. 

First delete took 6 minutes and memory has spiked up to almost 15GB in use out of 16GB physical. But the WSUS console (Update Services) still shows the same number of old updates. Failure? I don't think so: I'm running the cleanup wizard again and so far it isn't timing out... It has run over night, and has made some progress; the bar has moved perhaps 5%. 

So... My take is that the SQL server causes this problem when there is to much data, because the indexes are poorly designed (not because the indexes need to be re-indexed) causing the first query to time out, which causes the cleanup to fail. Once you get past that first deletion, and have everything loaded into memory, the cleanup tool can stay connected long enough to delete each unneeded update.

Next step will be to find a command line method, such as:
http://wsus.codeplex.com/releases/view/17612
and put it into the task scheduler like Microsoft should have done at the beginning to keep this from getting out of hand.

P.S. Lawrence Garvin, please do NOT reply to this; I have no need of your arrogance.

WSUS - Some Clients can't update

$
0
0
Hello everyone,
I am deploying a WSUS. The network (where is the WSUS and clients) is totally disconnected from the Internet. So, updates are downloaded on a WSUS with internet and exported to the WSUS of our local network.
The WSUS is a Windows Server 2016, clients are Windows Server 2016 and Windows 10 LTSB.
The updates work on Windows Server, no problem with that. But updates don't work with all Windows 10 LTSB.
Some W10 clients are updated but some can't.

They can report to the WSUS, I see them in the WSUS console but they can't update. When you go to the client you see the updates but they are blocked to 0%. I can see in the event log of Windows that the updates are starting to download. But few seconds after some of Windows update services are chrashing one by one (Windows update service,Windows Update OrchestraService,...). And the event log display that Windows Update found 0 update (after the crashes).
Can you help me with this problem, I'm lost right now and I don't know what I can try. Thanks

What I have already tried :
-WSUS GPO is fine (works on several computers)
-Firewall ok (same)
-Updates are approved of course
-Tried commands (like wuauclt, usoclient)
-Tried to remove the SUSClientID register key.
-Computers are installed from the beginning (We are not using the same image to install W10)
-I saw that a bug appeared with W10 LTSB and Windows Update. So, I pre-patched my computers with an update that should help (kb...16).

CVE-2019-1367 KB4522007

$
0
0

Hi all,

    Our company has been informed that CVE-2019-1367 (KB4522007,KB4522016, KB4522012) released on Sep 23th 2019. We need to patch these updates to our computers for security.

    But in KB4522007, it say KB only available on Microsoft Update Catalog but no available on Windows update & WSUS. On the other hand, I sync our WSUS and cannot find the update. So it seems to no way to push these KB via WSUS now.

    I just want to know if these KB  (KB4522007,KB4522016, KB4522012)  will be added into next security release in October 2019?

    As KB4522012 is for Windows 10 1709 which is not supported. WSUS will sync this KB in the future? Thanks in advance.

Regards,

Rick Tan

WSUS server fro Child domain

$
0
0

Hello Guys,

Is any procedure  for push the updates to child domain client from forest domain wsus server.And also how to push the updates to work group clients 

Regards,

Jaswanth

WSUS 2008 R2 server- all Win 10 shows Windows Vista

$
0
0

Dear Team,

Windows server 2008 R2 - WSUS running.

All Windows 10 shows Windows Vista.

Please suggest. 


Regards, Pradhap P

WSUS Best Pratice and Proxy is required or not?

$
0
0

Hello Team ,

We require you help on getting the below information for WSUS Install and Configuration :-

Infrastructure Details :-

 > We have Primary Domain Controller and secondary Domain Controller in UK  
 > The Fileserver also is configured in secondary Domain Controller 
 > We have RODC server in USA
 > We have Child Domain Controllers in Mumbai  

We have below Windows version :-

> Windows Server 2016 
> Windows Server 2012
> Windows 8
> Windows 10 


For the above infrastructure we need a Centralized WSUS Server where we can apply the updates effictively without any issues:-

1)Please let us know the Best Practice for the installation and Configuration settings to be done (GPO is preferred for our Infrastructure).

2)Do we require the reverse proxy for the WSUS ?

3)How to plan this update push to (Servers, Desktops) and what are the updates mandatory and what are updates should be avoided in the WSUS 

Thank You


install KB on remote computer

$
0
0

Hi,

I have some fer Server 2008 and Windows 7 machines on which 2019-09 patches failed.

I got a suggestion about missing prereq - KB from March that fixes the problem.

Since I cannot access workstations during business hours, I would like to install a particular KB remotely (even it was approved on WSUS but not reaching the workstation).

I found some solution that worked with previous powershell but stopped with newer versions.

(https://4sysops.com/archives/install-windows-updates-remotely-with-the-powershell/)

So, is there a way to install a particular KB on remote computer without hassle. Sure, I can copy it to remote pc.

Thanks.


--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

KB4517298 breaks Backup Exec 20.4

$
0
0

I have had so many issues this month with the August 13 updates.  Literally all of the OS's, servers and workstations broke in some way.  It's pretty crazy, most all issues are unique and removing does seem to fix some software but at the same time breaks many Windows functions like the taskbar and action center etc..

On one particular Windows Server 2012 R2, I am forced to remove KB4517298 and or KB4512488 or the Backup Exec user interface will not open.  The back end product runs fine and I can even remotely access it from another computer.  It's just for whatever reason the actual application simply won't run if either of those KB's are installed.

I hesitate to go to Veritas for support on this since I have half a dozen programs that simply won't function if either of these updates are installed.  It's not just Backup Exec, it's products from Blackbaud and other large organizations that were also broke by these updates.

I realize that on the release page, it does say the issue was solved by KB4517298:

https://docs.microsoft.com/en-us/windows/release-information/status-windows-8.1-and-windows-server-2012-r2

Unfortunately the issue is not resolved.  

The event viewer shows 3 events related to opening the Backup Exec UI:

Faulting application name: BackupExec.exe, version: 20.0.1188.2217, time stamp: 0x5cc09e57
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19425, time stamp: 0x5d26b6e9
Exception code: 0xe0434352

Application: BackupExec.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.AmbiguousMatchException
   at System.RuntimeType.GetMethodImpl(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Reflection.CallingConventions, System.Type[], System.Reflection.ParameterModifier[])
   at System.Type.GetMethod(System.String, System.Reflection.BindingFlags)
   at BackupExec.ThemeManager..cctor()

Exception Info: System.TypeInitializationException
   at BackupExec.ThemeManager.ChangeTheme(System.String, System.String)
   at BackupExec.App..ctor()
   at BackupExec.App.Main()

Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: BackupExec.exe
P2: 20.0.1188.2217
P3: 5cc09e57
P4: mscorlib
P5: 4.8.3928.0
P6: 5d3900b3
P7: 1139
P8: 61
P9: System.Reflection.AmbiguousMatch
P10: 

Attached files:

These files may be available here:
C:\Users\***********************\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_BackupExec.exe_bdfa4d408c93d84f9aa2534a7837169447f2d_8e7b3feb_1a28ccc2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2019c9f5-c524-11e9-8107-1866dafbd5ad
Report Status: 2048

The attached WER report is here:

Version=1
EventType=CLR20r3
EventTime=132109830570034369
ReportType=2
Consent=1
ReportIdentifier=2019c9f6-c524-11e9-8107-1866dafbd5ad
IntegratorReportIdentifier=2019c9f5-c524-11e9-8107-1866dafbd5ad
NsAppName=BackupExec.exe
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=BackupExec.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=20.0.1188.2217
Sig[2].Name=Problem Signature 03
Sig[2].Value=5cc09e57
Sig[3].Name=Problem Signature 04
Sig[3].Value=mscorlib
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.8.3928.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=5d3900b3
Sig[6].Name=Problem Signature 07
Sig[6].Value=1139
Sig[7].Name=Problem Signature 08
Sig[7].Value=61
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.Reflection.AmbiguousMatch
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=6cd4
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=6cd458e8d3a8156eab014cd5e8b92198
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=cbb8
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=cbb8e49be188d9a9cb61d20d49eb95c7
UI[2]=C:\Program Files\Veritas\Backup Exec\BackupExec.exe
UI[3]=BackupExec has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Veritas\Backup Exec\BackupExec.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\system32\SspiCli.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[13]=C:\Windows\system32\USER32.dll
LoadedModule[14]=C:\Windows\system32\GDI32.dll
LoadedModule[15]=C:\Windows\system32\IMM32.DLL
LoadedModule[16]=C:\Windows\system32\MSCTF.dll
LoadedModule[17]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[18]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[20]=C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[21]=C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[22]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\fe2524177eb3088c77be666722039f52\mscorlib.ni.dll
LoadedModule[23]=C:\Windows\system32\ole32.dll
LoadedModule[24]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[25]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[26]=C:\Windows\system32\uxtheme.dll
LoadedModule[27]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\e43dd9c73ab5615e461bf5109c3facd6\System.ni.dll
LoadedModule[28]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\0d59b0e237d7519417de10cd84bda4e7\System.Core.ni.dll
LoadedModule[29]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\40bd456a59a4969ec46e7d7fef6b5e32\WindowsBase.ni.dll
LoadedModule[30]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[31]=C:\Windows\system32\rsaenh.dll
LoadedModule[32]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[33]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\2e48700efecd23d15226baaa35a854bb\PresentationCore.ni.dll
LoadedModule[34]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\ec5e61c1f67279c3ebe8bd1160c680a7\PresentationFramework.ni.dll
LoadedModule[35]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\0212deecd5dfa435c6588fd68900ab8c\System.Xaml.ni.dll
LoadedModule[36]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[37]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[38]=C:\Windows\SYSTEM32\MSVCP140_CLR0400.dll
LoadedModule[39]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[40]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[41]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\4beb1eeca20b27d4bd1bb9880f03cc2a\System.Configuration.ni.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\5ee35debfc22f727e70e4479ddcbc045\System.Xml.ni.dll
LoadedModule[44]=C:\Windows\system32\shell32.dll
LoadedModule[45]=C:\Windows\SYSTEM32\SHCORE.dll
LoadedModule[46]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[47]=C:\Windows\system32\dwmapi.dll
LoadedModule[48]=C:\Windows\system32\psapi.dll
LoadedModule[49]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=BackupExec
AppPath=C:\Program Files\Veritas\Backup Exec\BackupExec.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5F52F6CA4553BDC12F4DF9EDDE73C968


Unable to upgrade Windows 10 Enterprise from 1809 to 1903

$
0
0

Hello,

I can upgrade my clients running Windows 10 PRO to May 2019 update (version 1903), but a client which is running Enterprise evaluation version 1809 does not receive 1903 upgrade from WSUS.

I downloaded both Feature update of Windows 10 business and consumer editions into WSUS console, with correct language as installed.

Do you have any advise/idea?

Thanks.

Riccardo

The WSUS Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 600000 milliseconds: Restart the service. 7031

$
0
0

I am having problems my WSUS is not showing under server manager after update installation, I have uninstalled all the updates and went through most forums for tricks nothing works. the error shown is 

The WSUS Service service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 600000 milliseconds: Restart the service. 7031

Update Services failed its initialization and stopped. 507

Server is not receiving software update from configuration manager

$
0
0

I have 3 windows Server 2012 R2 Machine which is not receiving patches from Last 3 Months from Configuration manager.

I have tried all the basic troubleshoots like Reset windows update components. 

Sfc/Scannow has been done after manual installation failed 

Manual update has been done - Failed

Windows Live update failed.

Here is the Logs:

WUAHandler Log

Failed to end search jobs error = 0x80240438

UpdateDeployment log

Job error (0x80240438) received for assignment ({90906EB7-3C83-4082-8674-11825202BDCC}) action 

Windows update log

2019-09-2909:56:36:37316562eccAgent  * WARNING: Failed to synchronize, error = 0x80240438

Import Button not available, only download, after selecting updates from catalog!!

$
0
0

Morning,

In a bit of a panic here this morning!!!. I have accomplished this many times in the not too distant past, now the feature is not available. All I get is a Download button followed which is followed by a Browse button to select where I want the updates downloaded to.???

There have been no changes to the server that I am aware of, and I login with admin rights to the server where I run the admin console from.!

Updates I have selected and are in the "basket":

KB2729094,2731771,2533623,2670838,2834140,2639308,2888049,2882822

WSUS Info: Server 2012R2, v6.3.9600.16384

Any and all assistance is greatly appreciated!!!

Tony

Powershell ComputerTargetScope

$
0
0

Hello,

this is driving me nuts... I'd like to use the "GetSummariesPerComputerTarget" method of the WSUS server object but only for a client target group with it's subgroups. Somehow I can't create a "ComputerTargetScope" object with a filter for the target groups in question??

Any idea?

__Leo


Windows Server 2016 DataCenter S2D Cluster Installs Windows Updates from Internet without permission

$
0
0

This weekend our cluster started, out of the blue, downloading and installing KB4516061.

This is strange behaviour because we have WSUS configured.

Settings  Group Policy Windows Update

- Configure Automatic Updates, Enabled, Auto Download and notify for install

- Specify intranet Microsoft update service location, Enabled, http://VWSUS1:8530

- Do not connect to any Windows Update Internet locations, Enabled

- Enable Client-side targeting, Enabled, W2016

BTW, this update KB4516061, is not on the WSUS server.

Disable "Update Settings" on WSUS clients

$
0
0

Hi,

we deployed WSUS on Windows Server 2019 and the the servers (as WSUS client) get the setting using GPO in the domain.

We want disable using GPO all "Update Settings" (Change Active Hours, Restart Options, Advanced Options) under"SETTINGS > UPDATE & SECURITY" to avoid that any account change these settings.

Unfortunately we could not find any GPO settings options in Administrative Templates.

Any idea?

Best regards

Birdal

Some WSUS clients are not displayed on WSUS console

$
0
0

Hi,

we deployed WSUS on Windows Server 2019. The servers (as WSUS clients) get the settings for updates using GPOs in the domain.

Although some servers have the identical settings, they will not listed in the WSUS console.

What is the issue here?

Best regards

Birdal

WSUS schedule monthly updates

$
0
0

Hello

Server WIN 2016 is deployed, settings for WSUS updates are configured as.

There is a problem with updating once a month. When configured, the server reboots every week.



On Win Server 2016




September 2019 SSU update not installing on some Server 2008R2 and 2012R2

$
0
0

Hi All

I have noticed that in September 2019 patching run, WSUS is failing to install the SSU update on more than half the fleet of servers, mainly the server 2008R2 and 2012R2. It is installing other patches OK and reboots the server, just not the SSU. Its not all its doing this to... but majority is like this. Previous months has been OK.. its just in September i have noticed this. Has others seen something similar? 
Thanks

DM

Viewing all 12331 articles
Browse latest View live


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