Jump to content
Welcome to our new Citrix community!
  • 0

Installing PV drivers (latest on) into W2012R2 keeps asking to reboot and xenserver network has yello exclamation mark

Roel Niesen




I already created a ticket with Citrix, but no succes yet.

I'm migrating some windows machinte from x2k8r2 to eventual w2k19.

I restored 1 server to the new server with ypervisor 8.2 fully patched.


When I install the pv drivers (nov 2020) I got this:

- wants to install storage driver over and over again

- xenserver network yell explimation maker


In c:\progamdata\citrix\installagent log I saw this:

- xenvin can no start child

- vbd needs to reboot


Now I got this extra error whenI install the driver:

Windows installer agent has failed.


Someone :)?



Link to comment

9 answers to this question

Recommended Posts

  • 0

Hopefully its not related to the version of XenServer and just an issue with the guest. Did you remove XenTools before you 

did the backup/restore? XenTools/Management Agent can get easily confused. I would make a backup/snapshot (messing

with XenTools can lead to boot issues/blue screens so you need something to revert back too).


I just did a migration from XenServer to VMWare and wrote a batch file to clean up the Xentools. I ripped out the main

part that you can run, reboot, and re-install XenTools again. Hopefully that will fix it.





REM Remove all c:\windows\inf files that are from Citrix
@echo off
for /F "delims=;" %%a in ('findstr /m /i "citrix" c:\windows\inf\*.inf') do (
@echo %%a
rem del %%a

REM Kill processes that will interfere with file deletion
REM Uninstall System Drivers
wmic sysdriver where name="xenbus" delete
wmic sysdriver where name="xendisk" delete
wmic sysdriver where name="xeniface" delete
wmic sysdriver where name="xennet" delete
wmic sysdriver where name="xenvbd" delete
wmic sysdriver where name="xenvif" delete

REM Delete Services 
sc delete XenAgent
sc delete XenBus_Monitor
sc delete XenLite
sc delete XenServerHealthCheck
sc delete XenSvc
sc delete XenPVInstall

REM Delete Registry Keys

REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenagent /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenbus /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenbus_monitor /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xendisk /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xeniface /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xennet /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenserverhealthcheck /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xensvc /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenvbd /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xenvif /f
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix /f

REM Set Recommended Registry for Disk Timeout
reg add HKLM\System\CurrentControlSet\Services\Disk /v TimeOutValue /t REG_DWORD /d 180 /f

REM Delete all of the files you can that aren't locked
del c:\windows\system32\xen* /Q
del c:\windows\system32\drivers\xen* /Q

REM Run Device Manager and remove any remaining 
REM Devices Manually. Check remove drivers if you
REM Have that option.

REM c:\windows\system32\devmgmt.msc

REM Delete all of the files again
del c:\windows\system32\xen* /Q
del c:\windows\system32\drivers\xen* /Q

RENAME Driver Files that may be in use
ren c:\windows\system32\drivers\xencrsh.sys alan1.sys
ren c:\windows\system32\drivers\xeniface.sys alan2.sys
ren c:\windows\system32\drivers\xennet.sys alan3.sys
ren c:\windows\system32\drivers\xenvbd.sys alan4.sys
ren c:\windows\system32\drivers\xenvif.sys alan5.sys

REM Save IP Information 

REM Reset Networking Adapters
REG DELETE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config /f


Link to comment
  • 0

Sorry to hear the script didn't work. Its going to only cover things I've ran into, and it of course be some other 

remnant of XenTools that I am not aware of. I take it you are installing the latest Management Agent version ?


Something else my script did that I edited out is once it completes I go into device manager and remove any

hidden devices. I didn't include that as it was another script that was embedded in the original. 




Link to comment
  • 0



So I got a very long chit chat and first they told that it wasn't supported.

Citrix tells that when you export an vm from xenserver 6.5 or 7.x and import it in hypervirosr 8.2 it is not supported.

But form the 4 machiens, 3 machines updated correctly => removed old drive and installed new driver.

Only in de windows domain controller it isn't working.

I see this on 2 cases (2 different costomers).

I was successfull to install xcp-ng 8.2  driver to have pv functionality.


Citrix tells me that that developing is looking for an fundamental change in how the driver will be installed.


The only bigg problem now is the automatic windows update.

Every time we do updates the not working 9.x drivers are installed.

I have to remove them everytime and then reinstall the xcp-ng drivers.


I tried to supress the 9.x drivers without luke.




Link to comment
  • 0
On 6/9/2021 at 6:25 AM, Roel Niesen said:

After 6 months, I received a beta driver that solves the issue.

So there was something wrong with the driver.


I'm testing it and than we will watch if the driver get public release to.



I just recently got my Xenservers and XenTools aka Citrix VM Tools updated... I'm getting this constant splat on my VDI desktops. 




I would like to get ahold of a driver that corrects this issue. 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...