SKY GO on a Virtual Windows Machine

Hi folks

anybody managed to get SKY GO to work on a Virtual Machine yet - under any virtualisation system (VBOX,VMWare,HYPER-V,KVM etc) --it installs OK but when you start it you just get left with a black screen. There's no problem running on a real machine and I can't see any mechanism that would forbid you to run this program on a VM if you are entitled to use the SKY GO application. The VM has plenty of horsepower so lack of processing power isn't an issue -- I regularly do video editing on this VM so the capability is there.

Even on an Esxi test server with graphics passthru to the guest it still won't work (at least for me)

Cheers
jimbo

thomaseg1 said:

Bandwidth?

Hi there

@thomaseg1

My Internet is > 10 Gb/s unlimited -- absolutely no problem on that front !!!!! regularly stream 4K UHD movies from Amazon / Netflix --these work on a VM too but since these run OK on a Linux Host - no probs as they use a browser - Firefox is the one I use so I use the HOST for those.

SKY GO is a separate application which isn't browser based and only runs on Windows but of course it needs the Internet to get content.

Cheers
jimbo

thomaseg1 said:

Just to be Clear, Your getting the full 10g in vm with no passthru drops?
Most of my vms have some drops, a couple to 60%.
Yes it does sound like I don't have it set right but I don't really run streaming Video in them.

Hi there

@thomaseg1

I don't like dual booting - but in this instance I've made a Windows to Go external SSD (connects via SATA-->USB C hi-speed connection) so I'll use that instead. I don't want to dual boot from the laptops internal SSD. The USB C interface boots blindingly fast so that might work OK when I want SKY GO when I'm travelling.

There's several easy ways of making a Windows to Go system without having to use "special certified devices" or start with an Enterprise version of Windows -- e.g Hasleo Wintousb or similar -- the trick also is to do the following after creating your WintoGo

a) rename the uaspstor.sys to uaspstor.sys.old or whatever you like

b) copy usbstor.sys to uaspstor.sys so you have 2 files which are really usbstor.sys !!! This seems to "poodlefake" the Windows system so it thinks it's running on "Disk C".

You'll probably need to logon to a Linux live system and attach the windowstogo disk to perform the name changes.

Now it should work -- if it fails first time use Macrium to "Fix Windows boot problems". It shouldn't though provided you DON'T boot the windows to go system before doing the name change.

Will post results later -- am just cloning a physical 1903 Windows 10 Pro system to a nice fast external SSD.

Cheers
jimbo

Hi there

@thomaseg1

Works perfectly -- created a wintogo from a current physical windows system on a desktop-- attached the SSD to my linux server where I renamed those windows files (they are in windows-->system32-->drivers)

removed and booted up on the Linux laptop (which I use on travels)

Works pefectly -- all activations fine etc etc.



Marking as solved as this method works and will in any case run better than streaming decent quality video via a VM anyway.

Cheers
jimbo