HKEY_USERS DEFAULT SHOWS CONSOLE and SYSNATIVE - WHY?

[abro89]

The OS is W7E-64b and in the registry HKEY_USERS there is a DEFAULT entry with reference to SYSNATIVE. The file is below copied from the HKEY_USERS hive. What is this entry and why is it there? Can I delete? I have used SYSNATIVE on other WIN OS's and there is no DEFAULT key and sub key contents starting with Console. Thx.....be safe.

 

[xrobwx71]

Hi,
Did you run our software? If not it's probably this. Hence our namesake. (toward the bottom of the page)

 

[abro89]

Thx for the reply. Its just an interesting curiosity. A few questions pls:

(a) can I delete this subkey "console"??( I already have a bkup image of the OS just in case)
(b) what software are you referring to when you say "did you run our software". I have used your repair tools on other machines and I have only run SFCFix.exe and a few tools from tweaking.com like tweaking.com_windows_repair_aio.zip.

Thx again...Sysnative is the best

 

[xrobwx71]

Thx for the reply. Its just an interesting curiosity. A few questions pls:

(a) can I delete this subkey "console"??( I already have a bkup image of the OS just in case)
(b) what software are you referring to when you say "did you run our software". I have used your repair tools on other machines and I have only run SFCFix.exe and a few tools from tweaking.com like tweaking.com_windows_repair_aio.zip.

Thx again...Sysnative is the best

(a) I wouldn't delete anything from the registry unless you are trained and know exactly what you're doing.

(b) The BSOD Collection App from here.

Thank you for the kind words!

 

[jcgriff2]

I doubt that the "SYSNATIVE" you see in the Registry has anything to do with this forum.

Look toward the bottom of post #1 - (16) ABOUT: Sysnative | Sysnative Forums - "Sysnative Brand/Logo"

The name Sysnative came from a Windows x64 Vista system. I had no idea what "sysnative" was at first.

Windows does not allow x64 and x86 (32-bit) anything to mix together.

\windows\sysnative is a virtual directory copy of \windows\system32 that is only visible to x86 apps that need to read the contents of \system32. If an x86 app tries to access \system32, it is redirected to \windows\syswow64 (the x86 version of \system32 - with differences).

So, x86 apps must hardcode for the app to read \sysnative and not the \system32 directory. This way, an x86 app absolutely cannot corrupt the pure x64 \system32 directory - because it never gets near it.

If you bring up an x64 Admin [B]CMD[/B] (hit WIN key; type CMD; (RIGHT-CLICk on CMD; select "Run as Administrator")); paste dir \windows\sysnative - nothing will be found.



Now, if you go to \windows\syswow64 and bring up an x86/32-bit Admin [B]CMD[/B] (RIGHT-CLICk on [B]CMD[/B]; select "Run as Administrator"), paste dir \windows\sysnative - you will see a ton of folders and files because it is a virtual copy of \windows\system32.

I just did a DIR for qu* - in \sysnative (1st line) - so you could see start-to-finish for a DIR command -



Anyway, that is where the name for this forum came from! :)

Regards. . .

jcgriff2

p.s. My BSOD app does not write to the Registry. I'm not sure about the Windows Update apps like SFCFIX.