https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDcyIiwiaGFzaCI6IjcxMGVmMTExLTVmYmUtNDFjZi1hM2UyLTg5Y2EyOTM3YzQ1MCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Microsoft Windows OS is stuck on boot screen after Veeam CBT driver is installed

Challenge

The Microsoft Windows OS is stuck on the boot screen after the Veeam CBT driver is installed.

Cause

The issue occurs if you have the Veritas System Recovery software installed on the Veeam Agent machine. The Veeam CBT driver is incompatible with the VTrack driver provided by Veritas. 

Solution

Resolve the issue in one of the following ways:
  • When your machine boots, press the F8 key before the Windows logo appears. Select the Last Known Good Configuration option.
  • Remove the Veeam CBT driver with Veeam Recovery Media. For details, see Removing CBT Driver with Veeam Recovery Media.
After the Veeam Agent machine is rebooted, remove the VTrack driver and install the Veeam CBT driver again. For details, see Installing Veeam CBT Driver.
KB ID:
3072
Product:
Veeam Agent for Microsoft Windows
Version:
2.0 or later
Published:
2019-12-24
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later