Windows Server 2019 Std, Cumulative updates are not installed

EugeneER

Member
Joined
Jan 16, 2024
Posts
8
Hi. Cumulative security updates have not been installed for several months. I tried through WSUS, SCCM and manual installation, the result is the same. I will be glad for any help.
 

Attachments

Hi and welcome to Sysnative,

Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.
Code:
dir /s /a %systemroot%\WinSxS\x86_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.1_none_79c5000be95fd03f > "%userprofile%\Desktop\Dirlist.txt"

Run also the following command and copy and paste the result in your next post.
Code:
reg query "HKLM\Software\Policies\Microsoft\Windows\DeviceInstall\Restrictions" /s
 
Code:
C:\>reg query "HKLM\Software\Policies\Microsoft\Windows\DeviceInstall\Restrictions" /s
ERROR: The system was unable to find the specified registry key or value.
 

Attachments

Open gpedit.msc and navigate to: Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.

Take a screenshot of this windows to see which policies are configured.
 
The setupapi.dev.log reports the following, so there must be a policy set somewhere? See also this document of Microsoft.

Rich (BB code):
>>>  [Device Installation Restrictions Policy Check]
>>>  Section start 2024/01/15 17:42:02.963
<<<  Section end 2024/01/15 17:42:02.986
<<<  [Exit status: SUCCESS]
 
Please check also the following:

1. Open the Server Manager click on Tools and launch the Group Policy Management.
2. Click on Forest: <name> > Domains > <name>.local > Employees.
3. Is here the Device Restrictions policy configured?
 
Sorry, but I couldn't find anything in group policies. Besides, they are not managed by me. But other servers in my domain are in the same conditions. And they have no problems installing updates.
 
Hi,

You're welcome. I am very curious about which policy or restiction is causing this problem.
 
Hello Maxstar.
I'm not sure this policy is the problem. All servers are under the same conditions. Messages "Device Installation Restrictions Policy Check" are on all servers in the setupapi.dev.log. The server was just broken :) I tried to fix it using the command
Code:
DISM /online /cleanup-image /restorehealth /source:WIM:B:\sources\install.wim:2 /limitaccess
but I get the error
Code:
Error: 0x800f081fThe source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
I use the installation disk as a source. I see a lot of errors in the "WindowsUpdate.log". In case you are interested, I will attach it too.
 

Attachments

Hi,

I've seen the message "Device Installation Restrictions Policy Check" only on system with specific restrictions / policies.

Could you please upload the latest CBS logs to look at the 0x800f081f error.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.
 
I you have a similar 2019 server (same patch level) in your network, I would suggest to run DISM with that server as source first. More than 26000 packages are missing or corrupted!

Replace "ServerName" with the correct name of the used source.
Rich (BB code):
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\Servicing\Packages\ /LimitAccess
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top