Unknown NT Operating System Code 10 Detected, windows 10

Hi,

Thank you for posting your query in Microsoft Community. We are glad that you have chosen Windows 10. But it is unfortunate that you are getting this error. Please let me help you resolve the issue.

In order to understand the issue in a better manner, please share the details.

1. What is the make and model of your computer?

Please follow the below method and see if it helps.

Method 1:

Run SFC Scan:
System file check is a utility built into the Operating System that will check for system file corruption. The sfc /scannow command (System File Check) scans the integrity of all protected operating system files and replaces incorrect, corrupted, changed, or damaged versions with the correct versions where possible.

Click on the below link,
http://answers.microsoft.com/en-us/windows/wiki/windows_other-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

If the issue persists, follow the below method.

Method 2:

Perform Clean Boot:

I suggest you to perform a Clean Boot and check if it helps.

To start your computer by using a minimal set of drivers and startup programs so that you can determine whether a background program is interfering with your game or program. This kind of startup is known as a "clean boot”.

Click on the below link,

https://support.microsoft.com/en-us/kb/929135

I hope the above information helps. If the problem persist, please feel free to replay back to us with the updated status. We will be happy to assist you further.

Thank you.

Every time I start Windows 10 I get a pop-up window that reads Unknown NT Operating System Code 10 Detected, followed by a second pop up window that reads "Read Config File Failed".  Thise messages appears twice an then desktop explorer "dies"

After the second round of error messages explorer ( the desktop ) shuts down and sceen goes in black, and I have to use task manager to start programs on my computer.   All my programs runs fine when I start them from task manager, exept the desktop.

If I start "explorer" from task manager the error messages comes back and explorer shuts down, and screen goes in black.

Any suggestions to fix this problem ?

The problem was soved by a reset of windows

Are you using a CardMan SmartCard reader?

If yes - check if there is an updated driver for it.

Hi !

I did a full reset of the computer and everything was ok. 

But when I installed drivers for my DisplayLink USB docking problem came back in a "light Version".    The error Message appears once after every restart, after clicking ok computer Works ok.

( I'm using a HP notebook )

Hi !

I did a full reset of the computer and everything was ok. 

But when I installed drivers for my DisplayLink USB docking problem came back in a "light Version".    The error Message appears once after every restart, after clicking ok computer Works ok.

( I'm using a HP notebook )

Hi!

I have the same "light" problem with my HP Pavillon DV6  notebook.

the error (with the second pop up windows "Read Config File Failed")  happens during the start up

and when I open the Control Panel page.

Error cmdiag "Unknown NT operating system code 10 detected"

I have tried the sfc scan. I have also ran ccleaner for a reg fix, and a clean boot.

Wish there was more on Microsoft site for this.

Its almost like Windows 10 does not know what Windows 10 is.

No solution as of yet.

I just installed installed Windows 10 too and I get cmdiag code 10 followed by the config file error at startup and at the control panel. None of the fixes seem to work. How do you reset windows.

I, too, had this problem after updating to Windows 10 from Windows 7.  My system would snarl at me (based on the Windows Nature theme I had installed at the time of update).  It has been quite annoying, but tonight, I got to the bottom of it.

I would get the "Unknown NT Operating System System Code 10 Detected", followed by "Read Config File Failed".  This would happen in pairs.  It wouldn't crash Explorer like some have reported; oh and I'd get it again when opening Control Panel.

So....

I started with the last "set" of errors (that of going to the Control Panel) to see if I could sneak up on it.

I went to my C:\ drive (the root of c:\), and then performed a global search for "*.cpl".

I found four flavors of cmdiag.cpl (one for Windows 2k, one for Vista, one for XP, and one simply named cmdiag.cpl.  The former OS flavors were located in one of the myriad Windows SideXSide folders.  Only cmdiag.cpl was in system32.  An Internet search helped me pinpoint what cmdiag.cpl was associated with. 

I have a Cherry Smart Card reader ST 1044U installed, and was working fine, but decided to poke around some.  And, obviously, the Cherry version I had originally installed for must have installed more than it needed to in terms of Windows SideXSide folders (i.e., this machine had never had Windows 2k or XP on it).  

I searched the Cherry web site and did find a newer install package, so I downloaded it.  I uninstalled the V1.9--merely executing the uninstalled blind without checking to see that it actually removed everything.  I then installed the new V3.3.  This did not change the status quo.

But I went back and re-ran the *.cpl search and saw something I missed before....

Of all the *.cpl files Search had found on my system, all of them had a 2015 install date (coincident with my upgrade date) EXCEPT the cmdiag.cpl associated files.  These sported a 2008 date.

This told me these objects did NOT undergo any metamorphosis stemming from the Windows 10 update (and was, therefore, "Unknown"--just like the error message was telling us).

So.  I temporarily renamed cmdiag.cpl to cmdiag.cpl.orig

Closed Control Panel and then re-opened it.

No more annoying Nature raspberry sound.

I knew I was onto something now....

I rebooted.

No more Nature raspberry sound at start-up, either....

Next, I looked in Registry and found 3 key references to cmdiag.cpl....  Thinking maybe the new Cherry software couldn't overcome some remnant of the older version left behind, I decided to do a more thorough uninstall/re-install.

I ran the uninstall of the new Cherry software.

I went into Device Manager, and right-clicked on my Smart Card reader and uninstalled the driver (and told the system to remove the software, too).  Next, I manually removed the Cherry directory that was left behind in Program Files (x86)----Note:  I have 32 bit Windows 10.

Lastly, I re-checked for "cmdiag.cpl" in Registry, and removed those 3 keys I had found earlier.  Obviously, the new Cherry package either did not remove these keys, or, no longer relied on them, and these were relics from the older V1.9 I had previously installed.  At-any-rate, they were orphaned, so I manually deleted them.

Of the 3 keys, I believe the one perhaps most problematic was the one that existed under HKLM_Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

At least, this would be in keeping with the "Unknown NT Operating System" part of the error.

Next, I rebooted and ensured the system came up (without annoying Nature raspberry sounds).

I then re-installed my new V3.3 Cherry software.

This package still seems to install the exact same version of the driver that had been previously installed, but conspicuously missing (i.e., NOT installed) is cmdiag.cpl. Cherry still provides a diagnostic mechanism--they just don't seem to do it via a control panel object.

Therefore, in my case, this was never a driver version, but rather simply the presence of cmdiag.cpl.

With this file (and its associated reference removed from Registry), I no longer have this problem.

For those who are experiencing this when opening Control Panel, perform a search for "*.cpl" and see if your "flavors" of cmdiag.cpl have a much older date than the date you performed the Windows 10 update.  If so, you've likely found the object causing the issue.  I suppose it's possible some other object could be causing it, too, but I'd expect to see a pre-update date for the culprit.

Hope this helps someone.  This is a far easier fix than Resetting Windows.

Good Luck.

M. Gentry