Registry question

I have actually never seen this error before, even on my own personal computers. Can you right click the registry folder and access any of the properties menu information? Or does this error message appear upon left or right clicking it? I would also check UAC permissions, even if it has worked in the past. Or Group Policy.

I also see that this specific registry folder has no Sub-Folders for you. I would try re-installing PC-DMIS to see if it creates the registry you are missing.


I've recently ran into an issue with IT where running PC-DMIS with the checkbox "Run as Admin" now flags a warning, and requires me to login to the "Administrator" account. Of which I have no access. The only way to open PC-DMIS now is for me to right click it, and run as Admin, as it isn't as elevated of a request. I still get a warning from UAC, but I can click to run it still. This is all on a Windows 11 Machine.

I have actually never seen this error before, even on my own personal computers. Can you right click the registry folder and access any of the properties menu information? Or does this error message appear upon left or right clicking it? I would also check UAC permissions, even if it has worked in the past. Or Group Policy.

I also see that this specific registry folder has no Sub-Folders for you. I would try re-installing PC-DMIS to see if it creates the registry you are missing.


I've recently ran into an issue with IT where running PC-DMIS with the checkbox "Run as Admin" now flags a warning, and requires me to login to the "Administrator" account. Of which I have no access. The only way to open PC-DMIS now is for me to right click it, and run as Admin, as it isn't as elevated of a request. I still get a warning from UAC, but I can click to run it still. This is all on a Windows 11 Machine.

The error message comes up when I open the registry and when I try to Right or Left click on the HKE_CURRENT_CONFIG.  It's only like this on this one machine.  The other 4 all look like your screenshot (which is what I'm used to seeing).  3 of the machines use the same generic login and would have the same permissions.

By some sort of miracle was a restore point created before the update? I would look into restoring, if that is even possible with a large update. Then after restoring, try from there after re-updating

Yes, it looks like that's an option.  I was hoping there would be another solution, because I can't imagine how long that would take.  My other machines are up for re-certification this week, so I'll likely have to deal with the saving issue for now while the others are down.

Did you try a hard reboot to see if it would clear that error?

No, just restarts.  I'll try a full shut down and see how it goes.  Thanks.