Del_Griffin
New member
- May 22, 2024
- 2
I have a Server 2022 install that is failing to install a cumulative update, from what I can see in the CBS log files I have issues within the "C:\Windows\WinSxS\amd64_microsoft-windows-s..rdatacenter-license_31bf3856ad364e35_10.0.20348.1194_none_42b88e9e669d00b0" folder when trying to run updates.
Examining similar issues posted on here I can see that your fixes essential copy over the contents from a working machine (I have one on another 2022 server, same build but patched with a newer cumulative update) and imports related elements within the Components hive.
I'm trying to build my own fix as I like to understand how this works should I need it in the future. Question is, do I need to copy files and components registry data from a server with the same build and cumulative update or will a same build with newer patches work just as well?
I'm trying this on a test restored VM in an isolated environment so I can break this as much as I want before testing in production.
Examining similar issues posted on here I can see that your fixes essential copy over the contents from a working machine (I have one on another 2022 server, same build but patched with a newer cumulative update) and imports related elements within the Components hive.
I'm trying to build my own fix as I like to understand how this works should I need it in the future. Question is, do I need to copy files and components registry data from a server with the same build and cumulative update or will a same build with newer patches work just as well?
I'm trying this on a test restored VM in an isolated environment so I can break this as much as I want before testing in production.
