XenServer 7.x HIR - BSOD system thread exception not handled

« Go Back
After completion of a Bare-Metal restore of a Xen 7.x Image in to dissimilar hardware/platform can result in BSOD "system thread exception not handled".
The installed Xen tools and Xen Drivers are causing a conflict in the environment due to the hardware being removed from the system and causing the system to BSOD on boot.

For test restores within a Xen environment, you can remove Xen Tools and then take a backup prior to the restore to prevent this issue from happening.

Steps for XenServer 7.0

Start by moving through the following article How To: Remove Hidden (Non Present) Devices after an HIR 

While still in safe mode/DSRM complete the following steps: 
  1. Open Administrative command prompt and implement the following commands to enable the MSI Server:
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver
  1. Run the uninstaller for Citrix Xentools (from programs and features), and reboot
  2. Load back in to safe mode - remove the following reg keys:
  1. Remove left over xen tools components from restored OS.
    1. Use administrative command prompt and navigate to C:\windows\system32 directory.
DIR Xen*.*
DEL Xen*.*
  1. Navigate to C:\windows\system32\drivers directory.
DIR Xen*.*
DEL Xen*.*
  1. Reboot in to Windows normal mode.

Steps for XenServer 7.1 and higher
  1. Boot the VM into the Windows PE based Recovery Environment.
  2. Open a command prompt by going to Tools > Command Shell 
  3. Load the Windows System registry hive from the boot volume.
reg load HKLM\restore c:\Windows\System32\config\SYSTEM
  1. Run regedit.exe from the command prompt.
  2. Browse to following registry locations. There maybe multiple keys with that name. Look through them to find UpperFilters keys with the value XENFLT:
  1. Right-click the UpperFilters key with the XENFLT entry and click Delete.
  2. For the remainder of the keys, search the registry (Ctrl+F) and search for XENFLT.
  3. Remove any keys mentioning XenFLT. Use F3 to search for the next instance.
  4. Close Registry Editor and unload the hive:
reg unload HKLM\restore
  1. Reboot

At this point, the machine should be able to boot into Windows correctly.

Recovery Environments - all
Article Details
Ryan Terres
10/19/2017 11:31 AM
Cory Nicholls
6/19/2018 10:54 AM

Powered by