Windows 10 Insider Preview Fast Build 19536 - December 16 Insider

Seems IP 19035 doesn't boot in vmware, not detecting a cd/dvd image during boot up stage.
ISO from MS IP site.

*lulz, got it to boot by changing boot order... wierd.
* damn, didn't realise how far behind i am on the version!

GunnzAkimbo said:

Seems IP 19035 doesn't boot in vmware, not detecting a cd/dvd image during boot up stage.
ISO from MS IP site.

*lulz, got it to boot by changing boot order... wierd.
* damn, didn't realise how far behind i am on the version!

Hi there

I gave up trying to install this build on VMWare but it works very well indeed as a VM on KVM/QEMU on a Linux host.

Note if you DO use this way of installing this build as a VM ensure you at VM create time (the easy way is with the libvirt method as it has an easy GUI wizard for installing VM's) you format the Virtual disk(s) as RAW, and use the virtio-win drivers: At Windows install time as well as the iso for the windows install--I created mine from UUPDUMP) ensure as a 2nd CD device have the virtio-win drivers iso added to the VM as well at creation. Get that iso from the fedora web site --you don't need fedora as your main Host - the virtio-win drivers are generic for Windows VM's

Then while installing you'll see Windows hasn't found a disk but in W10 there's a Load driver option --no more messing around with installing from floppy disks --remember that in W7 etc !!!!!! where you had to do all sorts of shenanogens to get drivers loaded for window install !!. Simply then open the CD and all proceeds brilliantly.

The Virtio-win drivers speed up the VM no end -- my Vm performs almost as good as the native version on a decent laptop.

Then also like creating VM's in HYPER-V set Bridged networking otherwise your VM will only have networking available to Internet --not the Host -- simply bridge a physical lan device to the virtual bridge.

What I like about this method (uses the spice video system -- you can pass thru graphics later if you need to) is 100% seamless operation of mouse and keyboard within the VM -- if the cursor is in the windowed VM area mouse and keyboard operates the VM -- if outside then focus is back to the host. You can also easily switch to full screen -- sound works pefectly and no problem accessing the Windows machine via RDP either locally or remote.

I'm now switching away totally from VMWare as it randomly has problems and my experience with VM's on KVM/QEMU makes them far more responsive than those on VMWare -- the only thing I haven't got yet --and I don't need it is 3D acceleration (2D hardware assist and acceleration is built in anyway which runs things like photoshop and VLC properly and I'm not a gamer).

Here's example of seamless Mouse in Windowed mode cursor is in my excel spreadsheet makes the whole thing so easy. Music player also playing and sound working perfectly.



If you do use Libvirt there's a built in graphical xml editor for the config files etc -- enable editing in the preferences in the Virtual Machine manager (Libvirt)



Cheers
jimbo

DooGie said:

My download has been stuck at 99% for the past 10 minutes

"It's better to be a fool for 5 minutes of your life by asking a question than to be a fool for the rest of your life by not knowing the answer."
I like this quote....

I keep getting these GSOD's when I log off. I have 19536.1000. It happens EVERY TIME I log off. When I log back in, I have the "Tell us what were you doing when Windows closed", or something to that effect. I have seen the GSOD a couple of times, but it doesn't stay up long enough for me to get a good look at what the error is. Event viewer shows "Error 12/28/2019 12:53:46 AM AppModel-Runtime 66 None" 69 times from 12/21/2019 to 12/28/2019.

I also had some 1800+ ESENT errors! I looked at a site, deskmodder.de, and they concluded it wasn't much to it, as their system was still running. Should I just report this to MS WIP and wait for them to fix it, or is there something that I can do to help resolve this?

CountMike said:

You could use Resplendence Software - WhoCrashed, automatic crash dump analyzer to find the cause afterwards.

Hi folks

there's always weird problems particularly on AMD systems if there's an option in the BIOS (MOBO BIOS) to enable IOMMU --- if this is enabled some systems won't even recognize any internal HDD's (although USB's are recognized).

IMO leave this disabled unless you are really messing around with trying to pass thru graphics on a VM -- and even if you get this working it usually hoses up internal NIC cards too so dubious if you can get any sort of consistent networking to operate consistently --you can get what's in the cache but new url's --forget it. !!!.

NOTE this is NOT the VT-D / VT-X virtualisation option --ensure that's enabled.

If you really HAVE to use the iommu on the amd bioss mobo settings at least in your Linux systems set grub with kernel parameter iopmmu_amd=yes iommu=pt and regenerate grub --system will then boot but if you can gthen get any nics to work --good luck.

I couldn't even get Windows to even see any HDD's until I disabled the IOMMU thing in the BIOS.

Bah Bah --Bye Bye AMD

Cheers
jimbo