Windows 10: Hyper V doesn't start Free Dos due to out of memory error

Recently I downloaded an iso of Free Dos and then I created a Free Dos Virtual Machine by using Hyper V and whenever I try to start this virtual machine I see the out of memory error all the time!

I still see this error even if I allocate a lot of memory for the virtual machine!
This also happened with all the different iso files of Free Dos!

Why I always see this out of memory error no matter what I do?
What's wrong with Hyper V?

:)

 

Hyper V doesn't start Free Dos due to out of memory error

Recently I downloaded an iso of Free Dos and then I created a Free Dos Virtual Machine by using Hyper V and whenever I try to start this virtual machine I see the out of memory error all the time!

I still see this error even if I allocate a lot of memory for the virtual machine!
This also happened with all the different iso files of Free Dos!

Why I always see this out of memory error no matter what I do?
What's wrong with Hyper V?

 

Windows doesn`t start. Authomatic repair doesn`t work.

Thanks again!!

I`m sorry I had not noticed that the text on the picture was in spanish. It says that windows has replaced some damaged clusters in "name" file and "directory". Then, at the end "an unspecified error occurred (75736e6a726e6c2e 4f6)".

I`ll do it and I`ll be updating this thread when I have the report.

- - - Updated - - -

I ran SeaTools. These are the results:




Does it mean my HDD is useless?

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?