The pool mount point (i.e. drive letter) is no longer available after updating

If you have recently updated Drive Bender and restarted your machine to discover your pooled drive(s) are no longer available, please do one of the following.

a) If you have at some stage upgraded from v1.4.0.1 or below, it may be that the old v1.4 driver is still installed. 

1. Download the legacy driver utility application from LegacyDriverUtility.zip 
2. Unzip the file to the Drive Bender folder (typically C:\Program Files\Division-M\Drive Bender) and run as an administrator. 
3. Select uninstall, then reboot.
4. If it still does not mount, continue with the following.
5. Under the start menu -> Drive Bender -> Driver utility (this is the same app, only for the new version of the driver). 
6. Select uninstall, then reboot. 
7. Once running again, open the utility again and select install, then reboot.

b) If you have never had v1.4.0.1 (or below) installed, do the following

1. Under the start menu -> drive bender -> driver utility (this is the same app, only for the new version of the driver). 
2. Select uninstall, then reboot. 
3. Once running again, open the utility again and select install, then reboot.

Upon the subsequent reboot, all mount point(s) should be available. We believe this issue is the result of the system components upgrade that has occurred either during this update, or a previous one (there was a major change to these components during the upgrade from v1.4.0.1 or below to v1.4.5.0 and above). We also believe that once the uninstall/reboot/reinstall happens, all future upgrades should process without issue.

Advanced troubleshooting

First and foremost, DO NOT delete any mount points and attempt to recreate them, this could result in lost data.

Next make sure it is actually gone. It is possible that the share may have gone missing, but the pooled drive is still available. Log on to the physical machine to check that the drive has actually gone. See this troubleshoot article before continuing.

The first thing you need to do is verify the Drive Bender system driver is installed and working correctly. To do this go to the Windows Start menu, then select Drive Bender, Driver Utility (this utility needs to be run with admin access to the machine, you can right-click and select "Run as administrator"). This utility is designed to check the state of the drive. First select "Check driver installation". This will report the status of the driver. If the status is not installed correctly, select "Install driver" and the reboot.

Once rebooted, open the utility again and perform the same steps to verify the drives installation. If still not installed correctly, contact support.

Next, assuming the driver is reporting that it is installed correctly, we need to check the Drive Bender service. First is it running? Check the Task Manager and look for "DriveBenderService.exe". We should also determine if it is the correct version that has been installed. Right-click the exe and check out the properties to make sure it is the correct version.

Now if all this checks out OK, then we need to look at the logs. The Drive Bender logs are located in the Drive Bender folder "C:\Program Files\Division-M\Drive Bender" (note on x64 machines this is NOT "Programs File (x86)"). The file name is db-xxxx-xx-xx-xx-xx-xx.sil (where all the xx's are the date). Please log a support ticket at http://support.drivebender.com.