Start a Conversation

Unsolved

S

8 Posts

1041

January 17th, 2020 20:00

SSD with Win10 from Optiplex 790 to Optiplex 9020 after sysprep - no boot drive

Trying to move my ssd from my Optiplex 790 to my Optiplex 9020. I ran sysprep which completed  OK.
In 9020 on trying to boot I get 'no boot drive found'.
In bios the boot options do not show the drive but under drives it shows up,

When I put the drive back in the  790 it boots up and starts the win 10 set up.  

What can I do to get it to boot in the 9020? 
Thanks 

4 Operator

 • 

5.6K Posts

January 18th, 2020 11:00

I am not sure why you are doing this.

Windows 7 can still be upgraded to Windows 10 free of charge as of a few days ago.

 

.

9 Legend

 • 

47K Posts

January 18th, 2020 12:00

The chipset is totally different.  You cannot move from one to another and run sysprep.

You have to reinstall from scratch with secure boot off.

Stop error code 0x0000007B (INACCESSIBLE_BOOT_DEVICE)

 

2 Intern

 • 

2.5K Posts

January 18th, 2020 14:00

9020

put a SSD in the blew slot, SATA,  and power.

with the USB stick made at  ms, WINDOW 10-64bit.  boot the stick and

fresh install, w10.

then set shares up on both PC and move or copy files,

you can not move disks. oK, for sure if UEFI is turned on, that be illegal (Microsoft activation fails) and lots more.

if you were in legacy mode it may try to boot but will (ethernet conn) will PnP for a week trying to replace all the wrong chip drivers,  I demo'd this to students, and was fun,  but UEFI NO WAY JOSe/'

then buy w10 OEM license (COA PRO) at ebay for $4.  go hog wild.  no really.

 

8 Posts

January 18th, 2020 15:00

Thanks for the reply

I was going by this 

https://www.youtube.com/watch?v=psuZpwk0zEE&t=1s

So this will not work then ? 

9 Legend

 • 

47K Posts

January 18th, 2020 18:00

Sysprep DOES NOT reinstall windows especially from MBR non uefi to GPT secure boot UEFI.

Causes of the Inaccessible_Boot_Device Stop 7b error

Any one of the following factors may cause the stop error:

  • Missing, corrupted, or misbehaving filter drivers that are related to the storage stack

  • File system corruption

  • Changes to the storage controller mode or settings in the BIOS

  • Using a different storage controller than the one that was used when Windows was installed

  • Moving the hard disk to a different computer that has a different controller

No Events found!

Top