Windows 10: BSOD error code PNP_DETECTED_FATAIL_ERROR was caused by windows 10 Virtual Machine.

This error occurred while I was starting up a VM Virtual Machine

and this popped up on my windows 10 with this error code:



\/

PNP_DETECTED_FATAIL_ERROR


Created by: Oracle

Version of VirtualBox: 6.1

Links: 1. www.oracle.com 2. www.virtualbox.org



I do not know why this happened but it just did!

:)

 

Clean install of W10 not possible in Virtual Machine.


@Kari

You can do clean install with windows 10 but it won't activate on Virtual Machine at least it didn't on mine. I followed the proper steps to do that.

Again I will repeat what I did step by step with some additions.

Step 1 Installed windows 7 retail on a virtual box, it activated without issue.
Step 2 changed the virtual box description to windows 10
Step 3 upgrade to windows 10 and it activated without issue
Step 4 backed up (So I could go back to it later)
Step 5 Removed windows 10.
Step 6 created a new virtual machine
Step 7 Installed clean windows 10 and it didn't activate and did that error code see below.


@night-hawk had a similar issue and got the same error code

Error code: 0xC004C003 with the specified product key being blocked

Night Hawk does it make a difference on what version of Virtual box that you are using?

My testing was done on Xubuntu using VirtualBox Graphical user interface version 4.3.26-Ubuntu r98988

 

Clean install of W10 not possible in Virtual Machine.


Please get a cup of coffee, lean back and think an answer for these two questions. Take your time, then check the answers below the questions:

Questions:

1. If you do a clean install of let's say Windows 10 Insider Build 10525 on a totally new computer which has never had an activated Windows 10 on it, does it activate?
2. If you do a clean install of Windows 10 Insider Build on a computer where the underlying Windows 10, upgraded from a qualifying old operating system has already been activated, does it activate?

Answers:

1. No, of course not.
2. Yes, of course.

Why do you think that a virtual machine would make any difference? You have tried to install Windows 10 on a totally new machine which has never had an activated Windows 10 installed, therefore the Microsoft activation servers block the activation due invalid machine ID. In the highlighted part in below quote you admit your mistake yourself, plain and simple, yet you when doing this wrong draw conclusion that even if done correctly it would not work:

What you have tried is essentially the same as if you took a brand new real physical PC without any operating system, which has never had any operating system, and then installed Windows 10 Insider Preview wondering why it does not activate! Virtual Machines behave exactly the same way; if you want to clean install Windows 10 Insider Preview and get it activated you must do it on an existing virtual machine, one which has already had an upgraded Windows 10 activated. This "computer", the virtual machine, its machine ID is marked on activation servers as valid and activated and it will of course activate.

Be it a virtual machine or a physical computer, you cannot activate a clean installed Windows 10 Insider Preview on a totally new machine. How difficult can this be to understand?

When clean installing Windows 10 Insider Preview on a computer which has already had a previous Windows 10 Insider activated, you do not use the product key! It will be asked twice, once before the installation starts and once after the last reboot to OOBE phase. In both cases you skip the product key and your Windows will be automatically activated.

 

Windows 10 BSOD Errors to Come with Troubleshooting QR-Codes

With its latest Preview Build (build 14316), Microsoft patched Windows 10 to make BSOD (blue-screen of death) errors more useful for system analysts and power-users. The blue-screen now puts up a QR-code to the knowledge-base page related to the error. Microsoft also set up an easy to remember URL at "windows.com/stopcode" for quick-reference to info and possible fixes to various kinds of errors.

The Register makes a valid case for how QR-codes in BSOD screens can be misused by malware developers. Malware or ransomware developers can now make their wares fake a BSOD screen with a QR-code that leads to their web-page to steal your information, or point you to download even more malware.





Source: The Register