Connect to the troubleshooting VM. Open Computer management > Disk management. Make sure that the OS disk is online and that its partitions have drive letters assigned.
Step 2: Repair or replace the corrupted file
Repair or replace the corrupted system binary (.sys) file by following these steps:
Repair the corrupt binary file
Open an elevated CMD prompt and run chkdsk on the disk:
Windows Command Prompt
chkdsk <drive-letter>: /F
Replace the corrupt binary file
On the attached disk, browse to the location of the binary file that's displayed in the error message.
Rename the file from <binary-name>.sys to <binary-name>.sys.old.
On the attached disk, browse to the \Windows\WinSxS folder. Then, search for the binary file that's displayed in the error message. To do this, run the following command at a command prompt:
Windows Command Prompt
dir <binary-name> /s
The command lists all the different versions of the binary file together with the created date. Copy the latest version of the binary file to the \Windows\System32\Drivers folder by running the following command:
E:\Windows\WinSxS>dir ACPI.sys /s
Volume in drive E has no label.
Volume Serial Number is A0B1-C2D3
Directory of E:\Windows\WinSxS\amd64_acpi.inf_0123456789abcdef_6.3.9600.16384_none_cdef0123456789ab
11/21/2014 07:48 PM 94,989 acpi.sys
1 File(s) 94,989 bytes
Directory of E:\Windows\WinSxS\amd64_acpi.inf_0123456789abcdef_6.3.9600.16384_none_89abcdef01234567
11/21/2014 07:48 PM 119,547 acpi.sys
1 File(s) 119,547 bytes
Directory of E:\Windows\WinSxS\amd64_acpi.inf_0123456789abcdef_6.3.9600.16384_none_456789abcdef0123
11/21/2014 04:06 PM 533,824 acpi.sys
1 File(s) 533,824 bytes
Total Files Listed:
3 File(s) 748,360 bytes
0 Dir(s) 123,967,512,576 bytes free
E:\Windows\WinSxS>copy E:\Windows\WinSxS\amd64_acpi.inf_0123456789abcdef_6.3.9600.16384_none_cdef0123456789ab\acpi.sys E:\Windows\System32\Drivers\
1 file(s) copied.
E:\Windows\WinSxS>
Note
If the system binary file can't be renamed, take ownership of the file. This action gives you full access to this file.
The example console output shows volume E as an example. The actual letter should reflect the faulty drive (the OS disk attached as a data disk on the troubleshooting VM).
If the latest binary doesn't work, you can try the previous file version to obtain an earlier system update level on that component.
If the only binary that's returned in this step matches the file that you're trying to replace on the affected VM, and if both files have the same size and time stamp, you can replace the corrupted file by copying it from another working VM that has the same OS and, if possible, the same system update level.
Learn to troubleshoot configuration issues that affect connectivity to your Azure-hosted Windows Server virtual machines (VMs). Explore approaches to resolve issues with VM startup, extensions, performance, storage, and encryption.