Windows Server 2016 - rješavanje zapisa grešaka iz preglednika događaja (Event Viewer) - 2. dio

Nastavljamo s uputama kako riješiti pojedine zapise grešaka iz preglednika događaja (Event Viewer) na OS-u "Windows Server 2016". Opširniji uvod napravili smo u prošlom članku, sada ćemo još samo ponoviti da smo isprobali sve što je ovdje navedeno, ali s obzirom na to da uvijek može doći do nekakvog izuzetka, sve ovo radite na vlastitu odgovornost i, ako možete, prije isprobajte u testnom okruženju.

05) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

U pregledniku događaja možemo vidjeti zapise kao što su dva niže navedena:

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          22.8.2017. 12:55:02

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          domena\korisnik

Computer:      imeservera.srce.hr

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{D63B10C5-BB46-4990-A94F-E40B9D520160}and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user domena\korisnik SID (S-1-5-21-2243945918-4202208769-3670398729-500) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="0">10016</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2017-08-22T10:55:02.454823200Z" />

    <EventRecordID>2011</EventRecordID>

    <Correlation />

    <Execution ProcessID="836" ThreadID="3016" />

    <Channel>System</Channel>

    <Computer> imeservera.srce.hr</Computer>

    <Security UserID="S-1-5-21-2243945918-4202208769-3670398729-500" />

  </System>

  <EventData>

    <Data Name="param1">application-specific</Data>

    <Data Name="param2">Local</Data>

    <Data Name="param3">Activation</Data>

    <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>

    <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>

    <Data Name="param6">domena</Data>

    <Data Name="param7">korisnik</Data>

    <Data Name="param8">S-1-5-21-2243945918-4202208769-3670398729-500</Data>

    <Data Name="param9">LocalHost (Using LRPC)</Data>

    <Data Name="param10">Unavailable</Data>

    <Data Name="param11">Unavailable</Data>

  </EventData>

</Event>

**********************************************************

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          22.8.2017. 12:54:31

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          NT SERVICE\MSSQLFDLauncher

Computer:      imeservera.srce.hr

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{D63B10C5-BB46-4990-A94F-E40B9D520160}and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT SERVICE\MSSQLFDLauncher SID (S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="0">10016</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2017-08-22T10:54:31.303893400Z" />

    <EventRecordID>2004</EventRecordID>

    <Correlation />

    <Execution ProcessID="836" ThreadID="3016" />

    <Channel>System</Channel>

    <Computer> imeservera.srce.hr</Computer>

    <Security UserID="S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582" />

  </System>

  <EventData>

    <Data Name="param1">application-specific</Data>

    <Data Name="param2">Local</Data>

    <Data Name="param3">Activation</Data>

    <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>

    <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>

    <Data Name="param6">NT SERVICE</Data>

    <Data Name="param7">MSSQLFDLauncher</Data>

    <Data Name="param8">S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582</Data>

    <Data Name="param9">LocalHost (Using LRPC)</Data>

    <Data Name="param10">Unavailable</Data>

    <Data Name="param11">Unavailable</Data>

  </EventData>

</Event>

Rješenje:

Ovo rješavamo podešavanjem prava u MSDTC konzoli (Component services).

Da bismo znali nad kojim objektom treba podešavati prava, prvo moramo pronaći ime objekta. To radimo pretragom u registryu.

Otvorimo registry bazu (regedit.exe) i napravimo pretragu za APPID u zapisu preglednika događaja. U našem slučaju to je ključ koji u imenu ima izraz "9CA88EE3-ACB7-47c8-AFC4-AB702511C276".

Kad pronađemo taj ključ, treba pogledati što piše pod "Default", obično je to "RuntimeBroker". To pamtimo jer je to ime objekta nad kojim ćemo podešavati prava u MSDTC konzoli.

Nakon toga treba trenutnom korisniku, najbolje administratoru, dati sva (Full) prava na taj registry ključ, jer su u protivnom postavke koje trebamo mijenjati zasivljene i zaključane u  MSDTC konzoli.

Da bismo mogli podešavati sigurnosne postavke nad tim registry ključem, treba promjeniti vlasnika (Owner) ključa i umjesto Trusted Installer staviti administratora:

- desni klik na ime ključa - Permissions...- Advanced - Owner - Change - Advanced - Find Now - selektirati administratora - ok - ok. Stavite pritom kvačicu i na Replace owner on subcontainers and objects i još jednom sve potvrdite klikom na OK. Time smo administratoru dali vlasništvo nad tim ključem, i nakon toga administrator može podešavati prava ili raditi druge radnje nad tim ključem.

Zatim dajte administratoru sva prava na taj registry ključ. Vjerujemo da te osnovne stvari znate, pa ne idemo baš skroz u detalje kako se nešto podešava.

Isti postupak u registry bazi (preuzimanje vlasništva i pridjeljivanje svih prava administratoru) treba primijeniti i nad CLSID ključem koji piše u zapisu preglednika događaja: "D63B10C5-BB46-4990-A94F-E40B9D520160".

Možete ga naći pretragom ili otvoriti direktni link:

HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}.

Zatim krećemo u podešavanja u konzoli Component services.

Iz grupe administrativnih alata otvorimo konzolu i proširimo je do popisa objekata: Component Services -> Computers -> My computer -> DCOM Config.

Našli smo da pod defaultom u registry bazi za APPID piše RuntimeBroker i to će biti naš objekt nad kojim podešavamo prava:

- desni klik na objekt - Properties - Security - Launch and Actvities Permissions - Customize - Edit, eventualno se može pojaviti Windows Security dijalog, gdje potvrdite "Remove".

Zatim u otvoreni dijalog za dozvole trebamo dodati sve račune koji se pojavljuju u zapisniku događaja pod SID, npr. NT AUTHORITY\SYSTEM SID (S-1-5-18...), NT SERVICE\SQLSERVERAGENT i slično, te im dati pravo Local Activation (defaultno imaju samo Local Launch).

Uglavnom treba dodati neke od ovih korisničkih računa:

SYSTEM

MSSQLFDILauncher

MSSQLSERVER

SQLSERVERAGENT

A nekad još i...

NT SERVICE\MSSQLSERVER

NT SERVICE\MSSQLFDLauncher

NT SERVICE\ReportServer

NT SERVICE\MsDtsServer130

Nakon što sve to podesite, zatvorite konzolu i restartajte servis "Distributed Transaction Coordinator" kako bi se promjene primijenile.

Ovdje treba spomenuti da neke od gore spomenutih korisničkih računa pri pokušaju dodavanja možda nećete vidjeti direktno na popisu, pa ih treba kopirati iz loga te ubaciti u polje za pretragu, i tada bi se trebali pojaviti.

Detaljnije o tom "problemu" možete pročitati na donjem linku (objašnjenje se nalazi negdje oko sredine stranice):

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for?forum=sqlsecurity.

Detaljnije o tome što koji SID (security identifier) predstavlja možete pronaći na linku:

https://support.microsoft.com/en-us/help/243330/well-known-security-identifiers-in-windows-operating-systems.

06) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID

{F72671A9-012C-4725-9D2F-2A4D32D65169}

U pregledniku događaja možemo vidjeti zapis kao niže navedeni:

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          22.8.2017. 13:28:52

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          SYSTEM

Computer:      imeservera.srce.hr

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}and APPID

{F72671A9-012C-4725-9D2F-2A4D32D65169}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="0">10016</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2017-08-22T11:28:52.168750600Z" />

    <EventRecordID>3009</EventRecordID>

    <Correlation />

    <Execution ProcessID="824" ThreadID="316" />

    <Channel>System</Channel>

    <Computer>imeservera.srce.hr</Computer>

    <Security UserID="S-1-5-18" />

  </System>

  <EventData>

    <Data Name="param1">application-specific</Data>

    <Data Name="param2">Local</Data>

    <Data Name="param3">Activation</Data>

    <Data Name="param4">{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}</Data>

    <Data Name="param5">{F72671A9-012C-4725-9D2F-2A4D32D65169}</Data>

    <Data Name="param6">NT AUTHORITY</Data>

    <Data Name="param7">SYSTEM</Data>

    <Data Name="param8">S-1-5-18</Data>

    <Data Name="param9">LocalHost (Using LRPC)</Data>

    <Data Name="param10">Unavailable</Data>

    <Data Name="param11">Unavailable</Data>

  </EventData>

</Event>

Rješenje:

Rješenje je prilično banalno, a svodi se na brisanje registry ključa APPID {F72671A9-012C-4725-9D2F-2A4D32D65169}. (Computer\HKEY_CLASSES_ROOT\AppID\{F72671A9-012C-4725-9D2F-2A4D32D65169})

Ako bismo, kao u prethodnom slučaju, htjeli napraviti podešavanja u konzoli MSDTC, to nam ne bi uspjelo jer pod defaultom ovdje piše "(value not set)", pa ne možemo znati nad kojim objektom treba podešavati prava.

Da bismo mogli obrisati taj ključ, trebamo podesiti vlasništvo i prava za administratora:

Desni klik na ime ključa - Permissions...- Advanced - Owner - Change - Advanced - Find Now - selektirati administratora - ok - ok. Stavite pritom kvačicu i na Replace owner on subcontainers and objects i još jednom sve potvrdite klikom na OK. Zatim mu još trebamo dati sva prava na taj registry ključ i nakon toga ga možemo izbrisati. Bilo bi dobro da prije toga za svaki slučaj napravite eksport ključa.

Nakon svega restartajte servis "Distributed Transaction Coordinator" kako bi se promjene primijenile.

Detaljnije:

https://www.tenforums.com/general-support/58449-local-activation-permission.html.

07) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID

{DB336D8E-32E5-42B9-B14B-58AAA87CEB06}

U pregledniku događaja možemo vidjeti zapis kao niže navedeni:

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          5.9.2017. 13:20:01

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          NETWORK SERVICE

Computer:      imeservera.srce.hr

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{2DC39BD2-9CFF-405D-A2FE-D246C976278C}and APPID

{DB336D8E-32E5-42B9-B14B-58AAA87CEB06}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="0">10016</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2017-09-05T11:20:01.336918700Z" />

    <EventRecordID>42920</EventRecordID>

    <Correlation />

    <Execution ProcessID="704" ThreadID="5572" />

    <Channel>System</Channel>

    <Computer>imeservera.srce.hr</Computer>

    <Security UserID="S-1-5-20" />

  </System>

  <EventData>

    <Data Name="param1">application-specific</Data>

    <Data Name="param2">Local</Data>

    <Data Name="param3">Activation</Data>

    <Data Name="param4">{2DC39BD2-9CFF-405D-A2FE-D246C976278C}</Data>

    <Data Name="param5">{DB336D8E-32E5-42B9-B14B-58AAA87CEB06}</Data>

    <Data Name="param6">NT AUTHORITY</Data>

    <Data Name="param7">NETWORK SERVICE</Data>

    <Data Name="param8">S-1-5-20</Data>

    <Data Name="param9">LocalHost (Using LRPC)</Data>

    <Data Name="param10">Unavailable</Data>

    <Data Name="param11">Unavailable</Data>

  </EventData>

</Event>

Rješenje:

Ova se greška javlja kad na Windows poslužitelju imamo instaliran SQL server. Podešavanja opet radimo u MSDTC konzoli.

Da se sad previše ne ponavljamo, jer smo postupak objasnili u prethodna dva slučaja, u registry bazi trebamo preko APPID-a pronaći o kojoj se komponenti radi. U našem slučaju to je "Microsoft SQL Server Integration Services 13.0". Za razliku od prethodnih slučajeva, ovdje je vlasnik ključa bio SYSTEM, a administrator je već imao sva prava nad ključem, pa ne trebamo ništa podešavati. Ime objekta nam treba radi MSDTC konzole.

Greška iz preglednika događaja inače se javlja jer nakon instalacije SQL-a, radi sigurnosti, nemaju svi korisnici dozvoljen pristup do Integration Services, pa ga za korisnika čiji se SID pojavljuje u zapisniku događaja trebamo ručno dodati u MSDTC konzoli (Component Services).

Otvorimo MSDTC konzolu i proširimo je do traženog objekta:
- Component Services -> Computers -> My computer -> DCOM Config - Microsoft SQL Server Integration Services 13.0 - desni klik na objekt - Properties - Security - Launch and Actvities Permissions - Customize - Edit, eventualno se može pojaviti Windows Security dijalog, gdje potvrdite "Remove".

Zatim u otvoreni dijalog za dozvole trebamo dodati račun koji se pojavljuje u zapisniku događaja pod SID, npr. NT AUTHORITY\ NETWORK SERVICE i slično, te mu dati pravo Local Activation (defaultno ima samo Local Launch).

Napravite restart servisa:

  • SQL Server Management Studio
  • Integration Services Service
  • Distributed Transaction Coordinator.

Detaljnije:

https://stackoverflow.com/questions/37727934/everytime-i-start-sql-server-agent-job-i-get-an-error-log

https://docs.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service

08) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{806835AE-FD04-4870-A1E8-D65535358293} and APPID

{EE4171E6-C37E-4D04-AF4C-8617BC7D4914}

U Event Vieweru nam se može pojaviti greška vrlo slična prethodnoj:

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          26.10.2017. 05:00:00

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          NT SERVICE\SQLSERVERAGENT

Computer:      imeservera.srce.hr

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{806835AE-FD04-4870-A1E8-D65535358293}and APPID

{EE4171E6-C37E-4D04-AF4C-8617BC7D4914}

to the user NT SERVICE\SQLSERVERAGENT SID (S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="0">10016</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2017-10-26T03:00:00.305130800Z" />

    <EventRecordID>26706</EventRecordID>

    <Correlation />

    <Execution ProcessID="736" ThreadID="9276" />

    <Channel>System</Channel>

    <Computer>imeservera.srce.hr</Computer>

    <Security UserID="S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430" />

  </System>

  <EventData>

    <Data Name="param1">application-specific</Data>

    <Data Name="param2">Local</Data>

    <Data Name="param3">Activation</Data>

    <Data Name="param4">{806835AE-FD04-4870-A1E8-D65535358293}</Data>

    <Data Name="param5">{EE4171E6-C37E-4D04-AF4C-8617BC7D4914}</Data>

    <Data Name="param6">NT SERVICE</Data>

    <Data Name="param7">SQLSERVERAGENT</Data>

    <Data Name="param8">S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430</Data>

    <Data Name="param9">LocalHost (Using LRPC)</Data>

    <Data Name="param10">Unavailable</Data>

    <Data Name="param11">Unavailable</Data>

  </EventData>

</Event>

Rješenje:

Već smo naučili da prvo preko APPID-a krećemo u pretragu registry baze kako bismo saznali o kojoj se komponenti u MSDTC konzoli radi i nad njom napravili potrebne promjene, odnosno dodali prava za korisnike kojima nedostaju.

APPID "EE4171E6-C37E-4D04-AF4C-8617BC7D4914" nam daje informaciju da se radi o "Microsoft SQL Server Integration Services 12.0". I ovdje nad tim ključem vlasništvo ima SYSTEM, a administrator ima sva prava, pa idemo na MSDTC konzolu.

Component Services -> Computers -> My computer -> DCOM Config - Microsoft SQL Server Integration Services 13.0 - desni klik na objekt - Properties - Security - Launch and Actvities Permissions - Customize - Edit, eventualno se može pojaviti Windows Security dijalog, gdje potvrdite "Remove".

Zatim u otvoreni dijalog za dozvole trebamo dodati račun koji se pojavljuje u zapisniku događaja pod SID, u ovom slučaju to je NT SERVICE\ SQLSERVERAGENT i dati mu pravo Local Activation (defaultno ima samo Local Launch).

U ovom slučaju treba napraviti restart servisa "SQL Server Agent (MSSQLSERVER)", jer se on vrti pod korisnikom "NT Service\SQLSERVERAGENT", a vidimo da taj korisnik nije mogao napraviti aktivaciju komponente. To možemo vidjeti u konzoli Services.

Nismo uočili da je potrebno, ali možete za svaki slučaj restartati i servise:

  • SQL Server Management Studio
  •  Integration Services Service
  •  Distributed Transaction Coordinator.

09) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{61738644-F196-11D0-9953-00C04FD919C1} and APPID

{61738644-F196-11D0-9953-00C04FD919C1}

Još jedna greška iz kategorije regedit -> MSDTC. Sve već znamo što i kako treba, pa ćemo ovo brzinski pojasniti.

Znači, u pregledniku događaja imamo zapis:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{61738644-F196-11D0-9953-00C04FD919C1} and APPID

{61738644-F196-11D0-9953-00C04FD919C1}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Pretraga registry baze preko APPID-a nam daje objekt "IIS WAMREG Admin service". Nad tim APPID i nad CLSID ključem preuzimamo vlasništvo i podešavamo prava za administratora, a zatim u MSDTC konzoli nad tim objektom podešavamo prava tako da pravo Local activation damo korisniku NT AUTHORITY\NETWORK SERVICE.

Restartati "Distributed Transaction Coordinator" servis.

10) Problem u servisu Windows Update

Svi znamo da je Microsoft s Windowsima 10 uveo dosta velike promjene u servis Windows Update. Ugrubo rečeno, najveća promjena je u tome što korisnici imaju jako malo opcija za podešavanje, a primarno i najvažnije je da ne mogu sami definirati kada će se i kako zakrpe preuzimati i instalirati. Sve je to sad, uglavnom, automatika. Eventualno u poslovnim okruženjima možete uvesti neki oblik kontrole preko WSUS ili SCCM servisa.

Novi GUI iz Settingsa može zablokirati u nekom "limbu" gdje je gumb Download zasivljen (ako je računalo na WSUSU) ili pri pokušaju provjere potrebnih nadogradnji postupak završi nekom greškom, te se nudi samo "Retry" (kad nije na WSUS-u).

Rješenje:

- Zaustaviti servise:

Windows Update -> net stop wuauserv

Cryptographic Services -> net stop CryptSvc

Background Intelligent Transfer Service -> net stop BITS.

- Preimenovati foldere:

ren %windir%\system32\catroot2 catroot2.old

ren %windir%\SoftwareDistribution sold.old.

Ako je računalo na WSUS-u, tada još treba obrisati registry ključ:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.

Brisanjem tog ključa postavke Windows Updatea vraćaju se na defaultne, kao nakon osnovne instalacije (provjera postojanja zakrpa tada ide preko Microsoftovih servera).

- Pokrenuti servise:

net Start BITS

net start CryptSvc

net start wuauserv.

- Pokrenuti Troubleshooter Windows Update za Windows (ovo možda može ići i kao prvi korak, ali rijetko pomaže bez ostalog, tu nismo uočili pravilo):

https://support.microsoft.com/hr-hr/instantanswers/512a5183-ffab-40c5-8a68-021e32467565/windows-update-troubleshooter.

Troubleshooter će vjerojatno pronaći problem s "Pending updates", pa izaberite "Apply fix...".

- Provjeriti nakon toga u Settings, trebalo bi biti omogućeno "Check for Updates", odnosno dok otvorimo konzolu, Downloading updates bi već moglo biti u tijeku.