Some WMI calls to UWF return access denied error

David S 21 Reputation points
2020-08-24T13:37:24.923+00:00

Hello,

I am currently working on a C++ application which uses the integrated write filter(UWF) of Windows 10 IoT.

I am using Windows 10 IoT Enterprise LTSC 1809 Build 17763.107

Now I face the following problem: Some WMI calls return with a "0x80041003 - Access denied" error and I can't figure out why. I have no problems to enable and disable the filter, commit files, query exclusions and even shutdown or reboot the system. But whenever I try to add or remove exclusions (file or registry), protect or unprotect a volume or enable the servicing mode I get the access denied error.

I have already tried/looked into the following things:

  1. The program is run locally from administator console with elevated rights
  2. The user account control (UAC) is deactivated
  3. COM security settings are (presumably) correct (dcomcnfg)
  4. WMI namespace permissions are (presumably) correct (WMImgmt.msc)
  5. WMI impersonation rights are (presumably) correct (gpedit.msc)
  6. The Administrator is in the Administators group (lusrmgr.msc)

The problem occurs with C++, C#, PowerShell and the WMI testtool (wbemtest). The only working way I found was the uwfmgr.exe.

My question is now how do I get the WMI calls to work properly? Are there any further setting I missed so far or are some of the WMI calls just not working?

Windows for IoT
Windows for IoT
A family of Microsoft operating systems designed for use in Internet of Things (IoT) devices.
399 questions
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,753 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sean Liming 4,601 Reputation points
    2020-08-24T15:18:18.847+00:00

    The UWF GUI utility I wrote is in C#. I have the servicing mode selection. You need to make sure that you are setting for the "next" session and not the "current" session. Trying to set the current session will fail!

    Regards,

    Sean Liming

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.