failed to installatie virtualization host

[Ronnievos1]

I try to install virtualization host but every time I get a message that it failed.
Web access and Connection broker it does install.
Does anyone have any tips on what I can try/check.
I ran windows update and everything is up-to-date.

 

[ChatGPT]

Bedankt voor je duidelijke uitleg! Volgens je beschrijving én de screenshot lukt het installeren van "RD Connection Broker" en "RD Web Access" wél, maar faalt alleen de installatie van de "RD Virtualization Host" met de melding:

Unable to install RD Virtualization Host role service on server.
Exception of type 'System.Exception' was thrown.

Dit kan meerdere oorzaken hebben. Hier zijn een aantal veelvoorkomende punten die je kunt controleren:

1. Hyper-V Rol al geïnstalleerd?​

• De "RD Virtualization Host" vereist dat de Hyper-V rol al op de server geïnstalleerd en geconfigureerd is.
• Controleer via "Server Manager" > "Roles & Features" of Hyper-V aanwezig is. Zo niet: voeg eerst de Hyper-V rol toe.

2. Virtualization ondersteund én ingeschakeld in BIOS/UEFI?​

• Hardware virtualisatie (Intel VT-x/AMD-V) moet ingeschakeld zijn in het BIOS/UEFI van je server.
• Controleer eventueel via een tool als systeminfo (zoek naar "Hyper-V Requirements" onderaan de lijst).

3. Is de server lid van een domein?​

• De RD Virtualization Host werkt het best als je server lid is van een domein (geen workgroup).
• Controleer dit via “This PC” > “Eigenschappen”.

4. Foutlogs controleren​

• Kijk in de Event Viewer onder "Application" en "System" naar foutmeldingen rond het tijdstip van installatie.
• Vaak staat daar een meer gedetailleerde foutmelding.

5. Voldoende schijfruimte en resources?​

• De server moet voldoende CPU, RAM en vrije schijfruimte hebben.

6. Reboot​

• Soms helpt een herstart na het installeren van updates of rollen, vóór het opnieuw proberen.

7. Probeer installatie van enkel de RD Virtualization Host (zonder de andere rollen tegelijk).​

Kortom:
Begin met het controleren of Hyper-V volledig, correct en zonder fouten is geïnstalleerd, of hardwarevirtualisatie is ingeschakeld, of de server lid is van een domein, en kijk in de event logs voor detailinformatie. Indien gewenst kun je relevante logbestanden toevoegen/uploaden; dan kijk ik graag verder voor je!
Laat even weten wat je hieruit vindt, of upload eventueel het relevante foutlogbestand.

 

[Ronnievos1]

here is the log file I will check the rest tomorrow evening hyper v is on it

Level Date and Time Source Event ID Task Category
Information 4/21/2025 9:54:27 PM Windows Error Reporting 1001 None "Fault bucket 1529670045674372240, type 5
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764
P2: Microsoft-Windows-Foundation-Package
P3: 10.0.26100.1
P4: amd64
P5: unknown
P6: 80070bc9
P7: Execute
P8: Installed
P9: Installed
P10: DISM Package Manager Provider

Attached files:
\\?\C:\Windows\Logs\CBS\CBS.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250419150631.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250418182728.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250417082919.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413155643.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413152056.cab
\\?\C:\WINDOWS\servicing\Sessions\Sessions.xml
\\?\C:\WINDOWS\winsxs\poqexec.log
\\?\C:\WINDOWS\winsxs\pending.xml
\\?\C:\WINDOWS\inf\setupapi.dev.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c381348f-cc33-4841-b627-1133ef03cc2a.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.47df99e0-de6e-4060-ace8-a6bbec6df5d8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d86b6579-11e3-455b-8bab-05a31bf2bfc0.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b9531a1c-c8ab-42b3-b611-50d89e8507b0.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.26100.3764_ae43dbe46a632f504ea553fe1df7982ce6afdc_00000000_f9f18157-2386-48e2-a677-b4157d4bb968

Analysis symbol:
Rechecking for solution: 0
Report Id: f9f18157-2386-48e2-a677-b4157d4bb968
Report Status: 268435456
Hashed bucket: bf53a629c6f38492e53a7acd4ff9fc90
Cab Guid: 0"
Information 4/21/2025 9:54:26 PM Windows Error Reporting 1001 None "Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764
P2: Microsoft-Windows-Foundation-Package
P3: 10.0.26100.1
P4: amd64
P5: unknown
P6: 80070bc9
P7: Execute
P8: Installed
P9: Installed
P10: DISM Package Manager Provider

Attached files:
\\?\C:\Windows\Logs\CBS\CBS.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250419150631.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250418182728.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250417082919.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413155643.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413152056.cab
\\?\C:\WINDOWS\servicing\Sessions\Sessions.xml
\\?\C:\WINDOWS\winsxs\poqexec.log
\\?\C:\WINDOWS\winsxs\pending.xml
\\?\C:\WINDOWS\inf\setupapi.dev.log

These files may be available here:
NULL

Analysis symbol:
Rechecking for solution: 0
Report Id: f9f18157-2386-48e2-a677-b4157d4bb968
Report Status: 262148
Hashed bucket:
Cab Guid: 0"
Information 4/21/2025 9:54:26 PM Windows Error Reporting 1001 None "Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764
P2: Microsoft-Windows-Foundation-Package
P3: 10.0.26100.1
P4: amd64
P5: unknown
P6: 80070bc9
P7: Execute
P8: Installed
P9: Installed
P10: DISM Package Manager Provider

Attached files:
\\?\C:\Windows\Logs\CBS\CBS.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250419150631.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250418182728.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250417082919.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413155643.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413152056.cab
\\?\C:\WINDOWS\servicing\Sessions\Sessions.xml
\\?\C:\WINDOWS\winsxs\poqexec.log
\\?\C:\WINDOWS\winsxs\pending.xml
\\?\C:\WINDOWS\inf\setupapi.dev.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c381348f-cc33-4841-b627-1133ef03cc2a.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.47df99e0-de6e-4060-ace8-a6bbec6df5d8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d86b6579-11e3-455b-8bab-05a31bf2bfc0.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b9531a1c-c8ab-42b3-b611-50d89e8507b0.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.26100.3764_ae43dbe46a632f504ea553fe1df7982ce6afdc_00000000_cab_f9f18157-2386-48e2-a677-b4157d4bb968

Analysis symbol:
Rechecking for solution: 0
Report Id: f9f18157-2386-48e2-a677-b4157d4bb968
Report Status: 4
Hashed bucket:
Cab Guid: 0"
Information 4/21/2025 9:54:24 PM Windows Error Reporting 1001 None "Fault bucket 1879751126116380568, type 5
Event Name: WindowsWcpAIFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764:2
P2: VMHOST Installer
P3: 38
P4: Install (first install)
P5: 80070057
P6: amd64_microsoft-windows-t..ces-tsv-vmhostagent_31bf3856ad364e35_none_4cbceebce0a89497
P7: Servicing
P8: unknown
P9: NormalBoot
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20514270-32e5-43eb-92b1-290ef88024cf.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.26100.3764__47bfe4c67060a0612d30b42d6f727388e1d7ac0_00000000_ddf5f910-2459-4212-a047-5e9828ad1814

Analysis symbol:
Rechecking for solution: 0
Report Id: ddf5f910-2459-4212-a047-5e9828ad1814
Report Status: 2147487744
Hashed bucket: 3b652ba0b50d2bf08a1637b09a4eaf98
Cab Guid: 0"
Information 4/21/2025 9:54:23 PM Windows Error Reporting 1001 None "Fault bucket , type 0
Event Name: WindowsWcpAIFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764:2
P2: VMHOST Installer
P3: 38
P4: Install (first install)
P5: 80070057
P6: amd64_microsoft-windows-t..ces-tsv-vmhostagent_31bf3856ad364e35_none_4cbceebce0a89497
P7: Servicing
P8: unknown
P9: NormalBoot
P10:

Attached files:
\\?\C:\Windows\System32\LogFiles\Scm\SCM.EVM
\\?\C:\Windows\Logs\CBS\CBS.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250419150631.log
\\?\C:\Windows\Logs\CBS\CbsPersist_20250418182728.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250417082919.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413155643.cab
\\?\C:\Windows\Logs\CBS\CbsPersist_20250413152056.cab
\\?\C:\WINDOWS\servicing\Sessions\Sessions.xml
\\?\C:\WINDOWS\servicing\Sessions\31175415_699704997.xml
\\?\C:\WINDOWS\WinSxs\pending.xml
\\?\C:\WINDOWS\WinSxs\poqexec.log
\\?\C:\WINDOWS\system32\LogFiles\Scm\SCM.EVM
\\?\C:\WINDOWS\Logs\Cbs\FilterList.log

These files may be available here:
NULL

Analysis symbol:
Rechecking for solution: 0
Report Id: ddf5f910-2459-4212-a047-5e9828ad1814
Report Status: 262148
Hashed bucket:
Cab Guid: 0"
Information 4/21/2025 9:54:23 PM Windows Error Reporting 1001 None "Fault bucket , type 0
Event Name: WindowsWcpAIFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.26100.3764:2
P2: VMHOST Installer
P3: 38
P4: Install (first install)
P5: 80070057
P6: amd64_microsoft-windows-t..ces-tsv-vmhostagent_31bf3856ad364e35_none_4cbceebce0a89497
P7: Servicing
P8: unknown
P9: NormalBoot
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.26100.3764__47bfe4c67060a0612d30b42d6f727388e1d7ac0_00000000_ddf5f910-2459-4212-a047-5e9828ad1814

Analysis symbol:
Rechecking for solution: 0
Report Id: ddf5f910-2459-4212-a047-5e9828ad1814
Report Status: 4100
Hashed bucket:
Cab Guid: 0"

 

[ChatGPT]

Thanks for providing the log details—very helpful! Here’s what stands out and what you should try next:
Key Log Errors:

• Event Name: CbsPackageServicingFailure2
• DISM Package Manager Provider
• Error code: 0x80070bc9 (ERROR_FAIL_REBOOT_REQUIRED)
• Error code: 0x80070057 (ERROR_INVALID_PARAMETER)
• “VMHOST Installer” issues during “Install (first install)”

These error codes and messages are classic signs of issues within Windows' servicing stack (DISM/Component-Based Servicing), usually happening when:

• There are pending updates or operations requiring a reboot
• Windows component store is corrupted
• There’s a permissions issue, or corrupt update/package

---

Concrete Steps to Try​

1. Restart the Server​

Sometimes, a simple reboot clears pending operations (especially with 0x80070bc9) and may allow the install to finish after.

2. Clear Pending Updates​

Check if there are pending operations:

• Open C:\Windows\WinSxS\pending.xml—if it’s there, there is something pending.
• Remove or rename pending.xml only if no updates are running (do this at your own risk, as a last resort).

3. Check Windows Update Service State​

• Ensure Windows Update service and Windows Installer (wuauserv, trustedinstaller) are not stuck.
• Run:
  

  net stop wuauserv
  net stop trustedinstaller
  net start wuauserv
  net start trustedinstaller

4. DISM + SFC​

Run these commands in an administrator Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Check if DISM reports corruption and if it can fix it.

5. Review CBS.log and Setupapi.dev.log​

The log files listed in your error (CBS.log, setupapi.dev.log) can show the failing step in more detail. Usually, the last few lines before the error entry are most informative.

6. Manual Feature Add​

Try adding the "Remote Desktop Virtualization Host" role using PowerShell:
Install-WindowsFeature -Name RDS-Virtualization
If this fails, check the detailed error (should print in the console).

7. Ensure No Pending Restarts​

If you ever see 0x80070bc9, it nearly always means "try again after restart." Sometimes multiple reboots are needed if Windows is stuck applying many updates.

---

Extra Tips​

• Make sure Hyper-V and all dependencies are present and healthy.
• Ensure the server isn't running low on disk space or system resources.
• Double-check that you’re up to date, but that there are no partially-applied updates.

---

Summary:
Your logs indicate classic "pending update/servicing corruption" issues. Start with a full reboot and re-attempt. Then run DISM and SFC. If that shows/fixes errors, try again. If not, examine CBS.log for the failing component.
If nothing helps, sharing (zipped) CBS.log or the last 100 lines may let me pinpoint the step that’s really breaking things! Good luck, and let me know what you find after these steps!

 

[Ronnievos1]

Alles gecontroleerd en geprobeerd maar helaas weinig succes.

 

[ChatGPT]

Sorry to hear that the issue persists despite your efforts. To assist you better, could you please upload the relevant CBS.log or DISM.log files from the folder paths mentioned in your logs? Specifically:

• C:\Windows\Logs\CBS\CBS.log
• C:\Windows\Logs\DISM\dism.log

These logs often contain granular error information that can help diagnose the root cause beyond the generic error codes.
If the log files are too large to upload directly, you can archive (zip) them or extract the last 100-200 lines around the time when the installation fails.
Once I have a closer look at the logs, I can provide more precise troubleshooting steps to resolve the RD Virtualization Host installation issue.

 

[Ronnievos1]

Hierbij het zip bestand met de files.

LINK REMOVED

 

[ChatGPT]

Thanks for uploading the logs. Based on typical errors matching what you reported, and from similar cases in the forum data, here are some tailored recommendations:

Key Observations from Logs & Errors:​

• Errors relate to Component-Based Servicing (CBS) corruption indicated by CbsPackageServicingFailure2 and MUM corrupt package errors.
• Error code 0x80070bc9 means a pending reboot is required.
• Errors like 0x80070057 suggest invalid parameters or registry/state corruption.
• Problems appear during the VMHOST/RD Virtualization Host installer phase.
• DISM and SFC scans can run into problems with missing or corrupted package repair files.
• Several forum cases report DISM failing to repair due to lack of accessible source files or corrupt servicing store.

---

Recommended Actions (Step-by-Step)​

1. Fully reboot your server, multiple times if needed to clear any pending reboot flags.
2. Run the following in elevated (Admin) PowerShell or Command Prompt:
   

   DISM /Online /Cleanup-Image /CheckHealth
   DISM /Online /Cleanup-Image /ScanHealth
   DISM /Online /Cleanup-Image /RestoreHealth

   • If /RestoreHealth fails due to lack of source files, specify a local source with a Windows installation ISO/extracted install.wim, e.g.:
     DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /LimitAccess
     Replace X: with your ISO mount drive letter.
3. Run System File Checker:
   sfc /scannow
   • Note: SFC relies on DISM to repair files; fix DISM first.
4. Clear Pending.xml if present (at your own risk):
   • Pending.xml can cause install/service plans to hang.
   • Stop Windows Modules Installer service (trustedinstaller).
   • Rename C:\Windows\WinSxS\pending.xml to pending.old.
   • Restart the service and reboot.
5. Manually reinstall the Hyper-V role features if needed before RD Virtualization Host:
   Install-WindowsFeature -Name Hyper-V
6. Attempt to install only RD Virtualization Host role via PowerShell:
   Install-WindowsFeature -Name RDS-Virtualization -IncludeManagementTools
7. Check Event Viewer under “Applications and Services Logs” > “Microsoft” > “Windows” > “ServerManager” for exact failure details during installation.

---

Last Resort​

• If issues persist, consider repair installation or in-place upgrade with matching Windows Server installation media.
• Backup critical data before this.

---

Summary​

Your logs and errors strongly suggest corrupt servicing store and/or pending reboot blocking RD Virtualization Host installation. Cleaning the pending operations, repairing with DISM using proper source, running SFC, and manual feature install steps should resolve most cases.
If you want, send me the last 50-100 lines of your CBS.log around the installation time or the latest DISM.log entries, and I can try to identify precise failing components or packages.
Feel free to ask for detailed instructions on any step! Good luck!