Immediate BSOD when running NTLite stable or beta

[phedders]

Help - can you please tell me why I cant run NTLite? I've installed the stable and Beta versions in a fresh Windows10 (1809) running in a KVM virtual machine - and when I run NTlite - I get immediate BSOD and stopcode. I havent got to the point where I can ender a licence key or use ntlite.

I should have tested before buying... Right now I have immediate buyers remorse.

Thanks

 

[phedders]

Argh. Closed it. Re-reran it... and it forced 1803 to crash too. Hmmm

 

[Clanger]

Best you can do now is work with nuhi.

 

[phedders]

Yea I'll wait for the next intructions - though I'm testing a few variations on 1803 too.

 

[phedders]

Quick summary

On 1803 if I "Run as administrator" it asks for permission... then runs ok.
On 1803 if I just run it, it asks for permission then crashes.

On 1809 (now with those 3 patches) - it crashes either way.

1803 is fresh - unpatched.

 

[Clanger]

Try PowerRun v1.3 (Run with highest privileges), you can run executables, registry files, batch and cmd files with the highest priviliedges, just drag stuff to its ui. Use it to change any greyed out services, drag services.msc(system32) to the ui.

 

[nuhi]

Quick summary

On 1803 if I "Run as administrator" it asks for permission... then runs ok.
On 1803 if I just run it, it asks for permission then crashes.

On 1809 (now with those 3 patches) - it crashes either way.

1803 is fresh - unpatched.

That doesn't sound like something NTLite can influence.
Can you please find some other tools which require the admin privileges to test if any of them is crashing?

Also does UAC disabling helps? Start - Run - "control" - User Accounts - Change User Account Control settings - Never notify
If that helps, try one notch above, does that run?

Thanks.

 

[Kasual]

Nooooo - does the same.

I've upgraded to KVM 3.1 too. Very annoying
I just want to make Win10 usable for VM run some access control software. If only Paxton would release a Linux version I'd be set

Could you try Virtual Box?

 

[Osbourne]

Sorry to resurrect this ancient thread, but did anyone find a solution to this?

 

[nuhi]

Yes, more info here (if confused, the key point is on this other link from the discussion):

Avoiding Blue screen of death on Windows [running on KVM]:

$ sudo -s
$ echo 1 > /sys/module/kvm/parameters/ignore_msrs

To make this permanent:
$ sudo nano /etc/modprobe.d/kvm.conf

Add this in:
options kvm ignore_msrs=Y
options kvm report_ignored_msrs=N

More official info here on KVM documentation. Why don't they adapt the KVM so it doesn't need that option, weird.
I wish I knew if possible to adapt the tool to not require that option, without losing anything.