1-800-691-1991 | 9am - 8pm ET
EN

Window Server does not boot because of stuck MPIO/SCSI registry records in SYSTEM hive

KB ID: 2365
Product: Veeam Backup & Replication
Version: All
Published: 2017-10-30
Last Modified: 2020-08-13

Challenge

When storage snapshot gets mounted to proxy Windows creates multiple registry records in:
HKLM\SYSTEM\ControlSet001\Enum\MPIO
HKLM\SYSTEM\ControlSet001\Enum\SCSI (when windows mpio is disabled)

The problem is that when storage snapshot gets unmounted Windows does not clean up registry records.
Eventually Windows will not boot when SYSTEM hive reaches 2GB (maximum size for system hive).

Cause

Based on Microsoft KB article it is behavior by design:
On a computer that's running Windows Server 2003 or a later version of Windows, a storage device that's connected through a fiber channel or through the iSCSI protocol may be connected for only a brief period. When a storage device is connected, Windows creates registry information for the device. Over time, the registry may contain many entries for devices that will never be used again. 

Solution

Microsoft recommends using DevNodeClean utility.
 
KB ID: 2365
Product: Veeam Backup & Replication
Version: All
Published: 2017-10-30
Last Modified: 2020-08-13

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.