3

I just installed Windows 10 a few days ago (Enterprise IoT).

Suprinsingly, if I open the "Start menu" and type "Device manager" and then Enter, I get this error:

enter image description here

It is:

Windows cannot access the specified device path or file. You may not have the appropriate permission...

(I will update this post to include a screenshot instead of photo as soon as I can).

Why this error? What is this GUID in the dialog box title?

Notes:

  • If I go in the Control panel, and click on "Device manager", it works.

  • I am doing this from main user of the computer (which is administrator).

  • Important update: the error comes if and only if we use this specific setup:

    • I created a key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell containing C:\myapp\myapp.exe to boot directly on my software, without Explorer (kiosk computer)

    • Then when I occasionally want to start the Windows desktop/Explorer anyway, I do CTRL+SHIFT+ESCAPE to run the Task Manager, then I run a new task from File > New task, then explorer. I tried both with "Run with admin privilege" checkbox checked or not.

    • Then, after this, from the newly started Explorer, the problem described on top is present.

    • Without this winlogon change, the problem is not present

Basj
  • 2,143

1 Answers1

4

To answer one question : The GUID corresponds to the Documents folder. You may test this by running Explorer with the full GUID as parameter:

explorer "shell:::{26EE0668-A00A-44D7-9371-BEB064C98683}\0\74246BFC-4C96-11D0-ABEF-0020AF6B0"

Such an error means some corruption and shouldn't be happening in a fresh Windows 10 install.

I suggest:


After the poster communicated the fact that the desktop was never launched during login, it is now clear that to get a desktop in this environment, Explorer needs to be launched inside the environment of the Windows login process. This is of course impossible, since this environment is not documented at all.

The final answer is that the above answer cannot work in this environment, so the answer is negative. The poster rejects the idea of starting and terminating Explorer immediately after login, so I can see no solution for the problem.

The only solutions I can see are either to use another login that has Explorer as its shell, or use a third-party Explorer replacement.

harrymc
  • 498,455