Difference between revisions of "Windows Stop 0x7B"
(Created page with "It's gone! No, not the error. The most useful web page for solving the issue is gone. It used to be here: http://support.microsoft.com/kb/314082/ That now redirects to this: https://docs.microsoft.com/en-US/windows/client-management/troubleshoot-inaccessible-boot-device And it isn't nearly as useful. Thankfully, there are some sites (including this one) which will preserve the ancient wisdom. == What this Article is About == This article is focused on the cloning...") |
m |
||
| Line 3: | Line 3: | ||
Thankfully, there are some sites (including this one) which will preserve the ancient wisdom. | Thankfully, there are some sites (including this one) which will preserve the ancient wisdom. | ||
== What this Article is About == | ==What this Article is About== | ||
This article is focused on the cloning of a computer. IE, using software like Acronis to copy a disk image of an existing computer to a new disk drive to be used in another computer. IE, again, if you have the perfect Windows X installation and want to use it on other physical machines (legally of course). | This article is focused on the cloning of a computer. IE, using software like Acronis to copy a disk image of an existing computer to a new disk drive to be used in another computer. IE, again, if you have the perfect Windows X installation and want to use it on other physical machines (legally of course). | ||
| Line 10: | Line 10: | ||
The below "Steps" are not for applying to a running computer (although it could be done ahead of time, before cloning). It's for applying to a Windows installation on a drive in an external USB docking bay (just as example to differentiate from the live / running / active disk inside of a computer) | The below "Steps" are not for applying to a running computer (although it could be done ahead of time, before cloning). It's for applying to a Windows installation on a drive in an external USB docking bay (just as example to differentiate from the live / running / active disk inside of a computer) | ||
== The Quick Summary == | ==The Quick Summary== | ||
The overall idea is to make sure Windows can boot on widely divergent hardware than it was originally installed on. Yes, there's lots of cloning software (including Acronis) that has the capability to do this (most of the time). But this is about doing it manually when none of the 'automatic methods | The overall idea is to make sure Windows can boot on widely divergent hardware than it was originally installed on. Yes, there's lots of cloning software (including Acronis) that has the capability to do this (most of the time). And Windows has quite a bit of capability to 'Repair...' an install. But this is about doing it manually when none of the 'automatic' methods work. | ||
In the specific example for the effort this article is based on, the source system used Intel RAID drivers (and was set as such in the computers BIOS Settings). But what if the destination computer doesn't have Intel RAID capability? Well, it's into the BIOS setting to change the SATA settings to IDE or AHCI (plus Windows Registry modifications too). | In the specific example for the effort this article is based on, the source system used Intel RAID drivers (and was set as such in the computers BIOS Settings). But what if the destination computer doesn't have Intel RAID capability? Well, it's into the BIOS setting to change the SATA settings to IDE or AHCI (plus Windows Registry modifications too). | ||
== The Steps (for experts) == | ==The Steps (for experts)== | ||
Try the afore mentioned 'automatic' methods of cloning to and from disparate SATA, M.2 / NGFF / NVMe, RAID 0, RAID 5, RAID WhatEver, etc. based computers. Try the 'automatic' 'Windows Repair'. If none of that works, well, that suck. Buckle up. And remember, you can also go from getting a single SATA based drive working on a new system, ''then'', cloning again to a RAID 0 NVMe set of Drives (for example) on the same system. This is just about getting a working Windows install on a new computer. | |||
Identify the destination computers capability (RAID (Intel or otherwise), IDE, AHCI, etc.) | Identify the destination computers capability (RAID (Intel or otherwise), IDE, AHCI, etc.) | ||
| Line 184: | Line 186: | ||
</syntaxhighlight>Mount the System Registry Hive in RegEdit (WhatEverExternalDriveLetter\Windows\System32\Config\System), using a weird, uniquely identifiable name like HappyDo (as in the example text above). | </syntaxhighlight>Mount the System Registry Hive in RegEdit (WhatEverExternalDriveLetter\Windows\System32\Config\System), using a weird, uniquely identifiable name like HappyDo (as in the example text above). | ||
== Source(s) of Some of the Information in this Article == | ==Source(s) of Some of the Information in this Article== | ||
https://mskb.pkisolutions.com/kb/314082 | https://mskb.pkisolutions.com/kb/314082 | ||
== Aftermath == | ==Aftermath== | ||
It worked. | It worked. | ||
And from there, one can use software like EaseUs to change from MBR to GPT if one has a 2 plus TB drive. | And from there, one can use software like EaseUs to change from MBR to GPT if one has a 2 plus TB drive. | ||
<br /> | <br /> | ||
Latest revision as of 07:06, 28 June 2022
It's gone! No, not the error. The most useful web page for solving the issue is gone. It used to be here: http://support.microsoft.com/kb/314082/ That now redirects to this: https://docs.microsoft.com/en-US/windows/client-management/troubleshoot-inaccessible-boot-device And it isn't nearly as useful.
Thankfully, there are some sites (including this one) which will preserve the ancient wisdom.
What this Article is About
This article is focused on the cloning of a computer. IE, using software like Acronis to copy a disk image of an existing computer to a new disk drive to be used in another computer. IE, again, if you have the perfect Windows X installation and want to use it on other physical machines (legally of course).
This article was written during the quest to clone a Windows 11 installation from an MBR based disk. Yup, MBR. Not a typo. It had to be done one section at a time from Acronis (because even Acronis wouldn't cooperate nicely, it even threatened to turn the MBR Drive into a GPT Drive).
The below "Steps" are not for applying to a running computer (although it could be done ahead of time, before cloning). It's for applying to a Windows installation on a drive in an external USB docking bay (just as example to differentiate from the live / running / active disk inside of a computer)
The Quick Summary
The overall idea is to make sure Windows can boot on widely divergent hardware than it was originally installed on. Yes, there's lots of cloning software (including Acronis) that has the capability to do this (most of the time). And Windows has quite a bit of capability to 'Repair...' an install. But this is about doing it manually when none of the 'automatic' methods work.
In the specific example for the effort this article is based on, the source system used Intel RAID drivers (and was set as such in the computers BIOS Settings). But what if the destination computer doesn't have Intel RAID capability? Well, it's into the BIOS setting to change the SATA settings to IDE or AHCI (plus Windows Registry modifications too).
The Steps (for experts)
Try the afore mentioned 'automatic' methods of cloning to and from disparate SATA, M.2 / NGFF / NVMe, RAID 0, RAID 5, RAID WhatEver, etc. based computers. Try the 'automatic' 'Windows Repair'. If none of that works, well, that suck. Buckle up. And remember, you can also go from getting a single SATA based drive working on a new system, then, cloning again to a RAID 0 NVMe set of Drives (for example) on the same system. This is just about getting a working Windows install on a new computer.
Identify the destination computers capability (RAID (Intel or otherwise), IDE, AHCI, etc.)
Copy the below text into a file to add to the registry. Wait! Don't just add it yet. Remember, this article is about when one is cloning a computer.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
;Add driver for Atapi (requires Atapi.sys in Drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
;Add driver for intelide (requires intelide.sys in drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00
;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00Mount the System Registry Hive in RegEdit (WhatEverExternalDriveLetter\Windows\System32\Config\System), using a weird, uniquely identifiable name like HappyDo (as in the example text above).
Source(s) of Some of the Information in this Article
https://mskb.pkisolutions.com/kb/314082
Aftermath
It worked.
And from there, one can use software like EaseUs to change from MBR to GPT if one has a 2 plus TB drive.