Windows 10 Build 9860 Now Available

sygnus21 said:

lehnerus2000 said:

sygnus21 said:

Anyway the other more annoying issue is I randomly get a memory notification telling me I don't have enough memory when the player tries to start Windows. I) I've got 32gig of system memory, 2) I've set the player to only use 4gig so I'm not sure what's going on. Anyway closing VM and re-opening it sometimes solves the issue, other times I have to wait a few minutes and try again. Weird.

So anyone else with VM issues?

I'm running a W10TP VM (2GB RAM allocated) with VMware Player on Linux Mint 17.

I haven't had any issues, but RAM allocation and/or reporting seems to work differently in the Linux version:

• LM17 normally uses ~450MB
• W10TP Task Manager reports that it is using ~650MB (it starts at ~900MB and then drops)
• Total RAM usage reported by LM17 is ~750MB

When I run VMs using VMware Wortkstation 7 on W7, the memory allocated to the VM is instantly deducted from my total available RAM.

Well having 32gig of RAM installed in my system should be a problem for VM to use say 4gig

Anyway I've not gotten the error again as of late but if I do I'll post a screen of the exact error reading.

Thanks.

lehnerus2000's post begs the question (again, I'm running a Hyper-V vm): How do you have memory set up in VMware? I'm VMware illiterate, so please excuse any ignorance I might display

If VMware has a dynamic memory setting (sounds as tough it might) and you have an initial setting lower than say, 2 GB, consider setting a static memory allocation. With 32 gigs you can afford 4 GB static.

Bill
.

First, the issue seems to have disappeared but if it re-appears, I'll post an image of it here. It seems moving the amount of RAM settings around solves it. I've currently got it set to use 4gig, had it as high as 6 and as low as 1 so...

As for this...

lehnerus2000 said:

We had VM issues when I did my Networking course (using VMware Workstation 7).
To avoid them, we created empty virtual HDDs and then installed Windows as if we were using real PCs with empty HDDs.

All I did was use an existing SSD drive that already had files on it. I created a folder and put the OS drive there. Maybe VM doesn't like to be split up like that? I know I've done it before when I tested Window 8.

Anyway we'll see what happens from here.

Thanks.

lehnerus2000 said:

sygnus21 said:

Well having 32gig of RAM installed in my system should be a problem for VM to use say 4gig

Anyway I've not gotten the error again as of late but if I do I'll post a screen of the exact error reading.

I saw that in your OP.
You definitely shouldn't be experiencing "Low RAM" warnings. :)

What do the Host and VM Task Managers say about your RAM usage when you see the message?

Perhaps there was a glitch when you created the VM and it is corrupted somehow.
Have you tried creating a new VM?

We had VM issues when I did my Networking course (using VMware Workstation 7).
To avoid them, we created empty virtual HDDs and then installed Windows as if we were using real PCs with empty HDDs.

I still build my VMs this way.

Maybe VMware Player glitched during its installation.

Since neither of us know about VMware I like this suggestion.

It might save some time if you look at Kari's latest tutorial:
ESD to ISO - Create Bootable ISO from Windows 10 ESD File

The last time I checked though, there's some discussion on install.esd and install.wim - I think it either depends on the origin of the ISO ('regular' or tech eval Enterprise) - I should go look, but...

If you don't have the install.esd, it should make it easier - you don't have to extract/decrypt the wim file from the esd.
I'm doing a lot of guessing now that Win10 is sucking up all of my time. :)

Bill
.

For now everything is working so I'm going to leave it. And, as I said before, I've currently got 4 gig of RAM allocated to it in VMware Player

Thanks.