VMware Cloud Community
gpouser
Contributor
Contributor

Unable to start the change tracking driver - Windows 2003 x64 - Not UAC as in Windows 2008 - Windows 7

I was trying to sync windows 2003 x64 to ESX 5.5 - napp-it in one storage, this failed. VMware Modified Clusters Tracking Driver test with "sc query bmdrvr" produced driver disabled on not in service.

I noticed on another server with windows 2003 x64 that worked on sync there was a reg key relating to bmdrvr to pointing to the  following location SysWOW64\drivers\bmdvr.sys, I exported the key and import to the server that was not working with sync, after that reboot to load registry and it still failed, but showed up on query, I removed two items from the key.

I removed "security" - "Enum" from the bmdrvr reg key and then tried to start, it worked. Why vConverter did not install this key on installing vConverter Stand alone on the Windows 2003 x64 does not make sense when it worked on the other system

C:\>sc query bmdrvr

SERVICE_NAME: bmdrvr

        TYPE               : 1  KERNEL_DRIVER

        STATE              : 1  STOPPED

                                (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))

        WIN32_EXIT_CODE    : 31  (0x1f)

        SERVICE_EXIT_CODE  : 0  (0x0)

        CHECKPOINT         : 0x0

        WAIT_HINT          : 0x0

C:\>sc start  bmdrvr

[SC] StartService FAILED 1058:

The service cannot be started, either because it is disabled or because it has n

o enabled devices associated with it.

Removed security - num keys from registry.

C:\>sc stop  bmdrvr

[SC] ControlService FAILED 1062:

The service has not been started.

C:\>

C:\>sc start  bmdrvr

SERVICE_NAME: bmdrvr

        TYPE               : 1  KERNEL_DRIVER

        STATE              : 4  RUNNING

                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))

        WIN32_EXIT_CODE    : 0  (0x0)

        SERVICE_EXIT_CODE  : 0  (0x0)

        CHECKPOINT         : 0x0

        WAIT_HINT          : 0x0

        PID                : 0

        FLAGS      

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr]

"Type"=dword:00000001

"Start"=dword:00000000

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):53,00,79,00,73,00,57,00,4f,00,57,00,36,00,34,00,5c,00,64,00,\

  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,62,00,6d,00,64,00,72,00,76,00,72,\

  00,2e,00,73,00,79,00,73,00,00,00

"DisplayName"="Modified Clusters Tracking Driver"

"WOW64"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Enum]

"0"="Root\\LEGACY_BMDRVR\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

First Export

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,57,00,4f,00,57,00,36,00,34,00,5c,00,64,00,\
   72,00,69,00,76,00,65,00,72,00,73,00,5c,00,62,00,6d,00,64,00,72,00,76,00,72,\
   00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Modified Clusters Tracking Driver"
"WOW64"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Security]
"Security"=hex:01,00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,\
   00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
   00,00,02,00,88,00,06,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
   05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
   20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,04,00,00,00,00,\
   00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,00,01,\
   00,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,00,18,00,fd,01,02,00,01,02,00,\
   00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,\
   01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Enum]
"0"="Root\\LEGACY_BMDRVR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

0 Kudos
1 Reply
gpouser
Contributor
Contributor

I hope this information helps with regards windows 2003 x64 or other fails on vCenter 5.5 or the like.

0 Kudos