That's strange.

I just tried to reproduce this with VMware Player 15, but it worked as expected.
Which host OS do you use? In case of Windows, please provide the build number too (e.g. 22H2).

André

It happened to me once before installing another OS, then I tried a couple times and it finally appeared but not anymore. I am on Windows 7 Ultimate Service Pack 1. Where can I loop up the build number?

A thought: In your virtual disk configuration, what bus type is configured. If it's SCSI, Windows XP may not have the drivers built-in, and you'd have to install SCSI drivers just like you would for a physical machine.

If the VM is set for a SCSI bus type for the hard drive, try changing it to IDE and see if the disk can be seen by the installer. 

W can I check that? Also, the issue is present for any operative system I try to install so I dont think its a Windows XP thing.

I'd start with reviewing the Workstation documentation. 

That is completely bizarre - I've never heard of anyone with this issue before.  Did you verify the installer's checksum?  Did you install as Admin?  The only thing I can think of is the files for the vmware-vdiskmanager utility didn't get installed and/or registered, so the system can't create/modify virtual disk files.

I know its weird specially because I have already 2 virtual machines installed but now I cant install a 3rd one because of this error. Is it possible to reinstall vmware player without losing my virtual machines>

VM are treated like documents, so you don't need to worry if you reinstall VMware Workstation. Just make sure that the current VMs are have been cleanly shut down, not suspended.

You may also want to verify that you run version 15.5. I'm not sure whether this will make a difference, but I checked the compatibility, and 15.5 is required for Windows 7 with Service Pack 1.

André

On my current OS I cannot upgrade from 15 to the newest Vmware version, right? I thought that might help if possible.

No, not to the newest version, but to v15.5.

André

Okay, I just upgraded now and the issue still persists. This is really getting on my nerves. Isnt there any way to debug this?

Thank you.

Not sure if some kind of log file is created. You may check whether there's on in %temp%.

Just to rule out permission issues, does this issue also occur when you start VMware Workstation with elevated permissions ("Run as Administrator")?

André

I've just tried the "Run as Administrator" tip but still no change. Does hard disk have to do with my physical hard disk or something?

>>> Does hard disk have to do with my physical hard disk or something?
Basically yes, but nothing special. A virtual disk is comprised of one or more .vmdk files. All you need is disk space.

Something else you may want to check, is whether your virus scan app detects the .vmdk files as false positives. I usually exclude *.vm* files in the VMs' folders from on-access scanning.

André

I dont think thats the case since no .vmdk files are being created just yet and I get no alert from Windows Defender whatsoever.