Cant boot after removing usb windows isntalator

[T15K6]

hello, installed windows 7 x64 with USB with (Use a Physical Disk option)  after that i want make snapshot but button is unclickable Gray color after this i remove that USB from wmvare settings and now i can make snapshot but after restarting or shutdown i cant boot in wvmare windows

[scott28tt]

@T15K6 

That disc is set as the boot device as per your screenshot but the VM BIOS is not finding a boot loader on it to start Windows. You may need to re-install Windows.

Not sure why you connected the second disc to the VM, it is usually the case that an OS installer ISO is attached to the CD/DVD drive of the VM.

[T15K6]

i do every time this with windows 10 but in some windows here is bug

reinstalling windows not helping

p.s when i install windows from CD rom its skip lot of steps and user creation steps too where i need Press CTRL+F3 to go sysprep because i use usb to install windows after that i test my usb installations in VMware 

[continuum]

Look at your screenshot with the configured Boot-order !
Removable Devices is still on top of the list !
So you have NOT fixed the boot-order.

Enter + to move the Hard Drive item to the top of the list !

Ulli

[continuum]

> p.s when i install windows from CD rom its skip lot of steps ...

When you install from ISO you probably use the easy-install feature.

If you install from USB you do the normal install. Results will differ !!!

Ulli

[T15K6]

@continuum  it does not matter first or secont i tested both its not work vmware are bugged 

p.s i dont use easy-install feature from ISO here is not option to choose this

[T15K6]

are you trolling me? 

[continuum]

> it does not matter first or secont i tested both

Wrong conclusion.
If both options fail it only means that you overlook an important detail. Could be an existing autoinst-flp or iso in the same directory.
Could be a bad entry in the vmx ...
Next step: FIX THE BOOTORDER !
Next step: START the VM AGAIN.
Then attach a directory listing, the current vmx-file and latest 3 vmware.logs to your next reply.

Ulli

[T15K6]

hi, i do that change bootorder HDD to first but same problem    

LOGS

[T15K6]

@continuum 

[T15K6]

@continuum 

@scott28tt 

hi, can someone help? 

[scott28tt]

@T15K6 

Nothing else I can think of, sorry.

[T15K6]

@scott28tt 

@continuum 
this bug seen 1-2 years if it possible to next version fix it?

[scott28tt]

@T15K6 

You'd need someone from the VMware Workstation team to answer that question. While I am an employee my role is not at all related to any of the product teams.

[continuum]

Still waiting for a file-listing.
Why do you have an active snapshot - when did you create the snapshot ?

Not sure why you say this is a bug ? - what makes you think so ?

[T15K6]

@continuum 

hey i share files what you ask

https://communities.vmware.com/t5/VMware-Workstation-Pro/Cant-boot-after-removing-usb-windows-isntal...

https://communities.vmware.com/t5/VMware-Workstation-Pro/Cant-boot-after-removing-usb-windows-isntal...

[continuum]

Still waiting for the filelist ...
Why do you assign the virtual disk twice ?
scsi0:0.fileName = "Windows 7 x64-000001.vmdk"
scsi0:1.fileName = "Windows 7 x64-000001.vmdk"
?

[T15K6]

@continuum 

yo bro i add filelist what u ask you ask logs

vmware.log

vmware-0.log

vmware-1.log

vmware-2.log

and

Windows 7 x64.vmx

what you want more i dont understand

[continuum]

Examples for a filelist:

 or

Directory of G:\_vms_\debian10-mini

02/11/2021 08:02 PM <DIR> .
02/11/2021 08:02 PM <DIR> ..
01/20/2021 02:04 PM <DIR> data.vmdk.lck
01/20/2021 02:04 PM <DIR> data-000001.vmdk.lck
01/05/2021 04:37 PM <DIR> Debian 8.x.vmx.lck
01/20/2021 02:04 PM <DIR> Debian 8.x-fa0b4b50.vmem.lck
01/20/2021 02:04 PM <DIR> debian10-mini.vmdk.lck
01/20/2021 02:04 PM <DIR> debian10-mini-000001.vmdk.lck
01/20/2021 02:04 PM <DIR> gpt-example.vmdk.lck
01/20/2021 02:04 PM 0 vmware.log
01/20/2021 08:47 AM 1,314,274 vmware-0.log
01/05/2021 06:56 PM 328,586 vmware-1.log
01/05/2021 04:40 PM 203,098 vmware-2.log
01/28/2021 03:20 AM 74,232 Debian 8.x.nvram
02/11/2021 08:02 PM 0 filelist.txt
01/07/2021 12:42 AM 597,491,712 data.vmdk
01/20/2021 02:07 PM 8,585,216 data-000001.vmdk
01/07/2021 12:42 AM 5,163,384,832 debian10-mini.vmdk
01/20/2021 02:05 PM 5,503,582,208 debian10-mini-000001.vmdk
01/20/2021 08:47 AM 238,419,968 gpt-example.vmdk
01/06/2021 12:14 AM 4,294,967,296 Debian 8.x-fa0b4b50.vmem
01/07/2021 12:48 AM 4,294,967,296 Debian 8.x-Snapshot1.vmem
01/07/2021 12:42 AM 527 Debian 8.x.vmsd
01/07/2021 12:48 AM 5,766,716 Debian 8.x-Snapshot1.vmsn
01/20/2021 02:05 PM 3,123 Debian 8.x.vmx
01/05/2021 04:37 PM 265 Debian 8.x.vmxf
17 File(s) 20,109,089,349 bytes
9 Dir(s) 140,117,331,968 bytes free

[T15K6]

08.02.2021  17:45    <DIR>          .
08.02.2021  17:45    <DIR>          ..
08.02.2021  00:29           191 096 vmware-0.log
07.02.2021  19:53           190 634 vmware-1.log
07.02.2021  03:42           249 008 vmware-2.log
08.02.2021  17:38           249 742 vmware.log
05.02.2021  17:17               691 Windows 7 x64-0.vmdk
07.02.2021  03:40       166 002 688 Windows 7 x64-000001-s001.vmdk
07.02.2021  03:40        61 865 984 Windows 7 x64-000001-s002.vmdk
07.02.2021  03:40           589 824 Windows 7 x64-000001-s003.vmdk
07.02.2021  03:40       772 931 584 Windows 7 x64-000001-s004.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s005.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s006.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s007.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s008.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s009.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s010.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s011.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s012.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s013.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s014.vmdk
06.02.2021  02:53           524 288 Windows 7 x64-000001-s015.vmdk
06.02.2021  02:53            65 536 Windows 7 x64-000001-s016.vmdk
07.02.2021  03:16             1 082 Windows 7 x64-000001.vmdk
07.02.2021  03:16               691 Windows 7 x64-1.vmdk
07.02.2021  03:41               691 Windows 7 x64-2.vmdk
05.02.2021  18:19     3 567 452 160 Windows 7 x64-s001.vmdk
05.02.2021  18:19     4 075 487 232 Windows 7 x64-s002.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s003.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s004.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s005.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s006.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s007.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s008.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s009.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s010.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s011.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s012.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s013.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s014.vmdk
05.02.2021  17:16           524 288 Windows 7 x64-s015.vmdk
05.02.2021  18:19           131 072 Windows 7 x64-s016.vmdk
05.02.2021  18:23     3 254 779 904 Windows 7 x64-Snapshot1.vmem
05.02.2021  18:23       136 029 823 Windows 7 x64-Snapshot1.vmsn
08.02.2021  17:38             8 684 Windows 7 x64.nvram
05.02.2021  17:19             1 136 Windows 7 x64.vmdk
05.02.2021  18:19               484 Windows 7 x64.vmsd
08.02.2021  17:38             3 007 Windows 7 x64.vmx
06.02.2021  02:53               268 Windows 7 x64.vmxf

@continuum 

[continuum]

That helps ...

During last few days you moved "Windows 7 x64-000001.vmdk" from scsi0:1 to scsi0:0

Please look up which scsi port is used in the vmsd-file - and if you have a hexeditor - also look it up in the vmsn-file.