Closed LittleNyanyay closed 3 months ago
I'm not sure what's happening in this command, on the surface it says access denied. The powershell has administrator rights and the service is working. windows11 professional workstation edition 23H2 22631.3880
Hi,
so about this part
I checked C:\Program FilesWDACConfig\StagingArea\New-KernelModeWDACConfig\KernelModeDriversDirectory while the command was running and all files in this directory were 0kb
This is expected. Those are symlinks to the files to be scanned, not the actual files.
The rest of the errors appear to be only related to the ShadowCopy service. Currently, the WDACConfig module offloads all of the file scanning operations to the built-in cmdlets of the ConfigCI module but soon i'm planning on implementing the entire logic myself, customized for the module's requirements.
I've never ran into the access denied issue with ShadowCopy before though, but i know the built-in ConfigCI module has a known issue with ShadowCopy service, I've talked about it here
https://github.com/MicrosoftDocs/WDAC-Toolkit/issues/302 https://github.com/MicrosoftDocs/WDAC-Toolkit/issues/362
I'll keep you posted when i know more about this, i'll try to reproduce it myself too
So it's been over a week and I still can't reproduce this error. I'm fairly certain it's a problem on your end, most likely caused by a 3rd party program or configuration, if you test it on a clean system you will see the problem you're experiencing won't happen.
Doing a Bing search for Volume Shadow Copy Service Error: hr = 0x80070005, Access is denied
you can find multiple articles offering fixes, so i suggest trying the out see if they will fix it.
Also, you have other options for creating a strict kernel-mode enforced policy.
You can use this command to deploy the audit mode policy first as you normally would
New-KernelModeWDACConfig -Mode Prep -Deploy
Then restart your system and use the following command (Change policy path if you need to)
ConvertTo-WDACPolicy -BasePolicyFile "C:\Program Files\WDACConfig\DefaultWindows_Audit_Kernel.xml" -KernelModeOnly -Deploy
I created it specifically for this purpose. It gives you even more control over which .sys
files will be included in the enforced mode policy.
Then remove the audit mode policy using the following command
Remove-WDACConfig -UnsignedOrSupplemental -PolicyNames <Strict Kernel Audit mode Policy Name>
Note that It has one caveat at the moment, it doesn't support WHQLFilePublisher
, it supports FilePublisher
, Publisher
, Hash
levels.
Support for WHQLFilePublisher
for ConvertTo-WDACPolicy
will be added in a future update along with the reduced reliance on built-in modules that I mentioned in earlier comments.
Documentations:
Tools category
WDACConfig Module
Does Your System Meet The Requirements?
Is your Windows Installation Genuine?
Did You Read The Frequently Asked Questions?
Please Explain The Bug
New-KernelModeWDACConfig -Mode Prep -Deploy after this command and reboot .
Next use the command: New-KernelModeWDACConfig -Mode AuditAndEnforce
Description of the phenomenon:
Error Details