Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: 'Disable System Guard rule definitions': The process cannot access the file because it is being used by another process #497

Open
ElektroStudios opened this issue Jan 26, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@ElektroStudios
Copy link

ElektroStudios commented Jan 26, 2025

Description

The following script with description:

  • --- Disable System Guard rule definitions

Is causing the following error messages:

Failed to rename "C:\Windows\System32\Sgrm\SgrmAssertions.bin"
to "C:\Windows\System32\Sgrm\SgrmAssertions.bin.OLD":
The process cannot access the file because it is being used by another process.

Failed to rename "C:\Windows\System32\Sgrm\SgrmAssertions.cat"
to "C:\Windows\System32\Sgrm\SgrmAssertions.cat.OLD":
The process cannot access the file because it is being used by another process.

FullyQualifiedErrorId: Microsoft.PowerShell.Commands.WriteErrorException


Partial output (in Spanish):

sexy_Disable System Guard rule definitions.txt


How can the bug be recreated?

No exact idea. ¿Maybe having the same Windows 10 OS build I have, and running the Privacy Sexy generated script file that I've attached?.

I really don't have any running third-party application that could have open (reading/writing/using) SgrmAssertions.bin and SgrmAssertions.cat files. Probably the operating system itself is who is using them... I'm not sure whether executing the Privacy Sexy generated script file in Secure Mode would be able to rename those files.

Operating system

Windows 10

  • Version: 10.0.19045.2006
  • Architecture: 64-Bit
  • Edition: Home Single Language
  • OS Language: Spanish of Spain (es-ES)
  • User account privileges: Built-in "hidden" Administrator account, with UAC disabled.

Script file

PrivacySexy.zip

Screenshots

Image

Additional information

Tested with Privacy Sexy version 0.13.7

PowerShell $PSVersionTable output:

Name                           Value
----                           -----
PSVersion                      5.1.19041.1682
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1682
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@ElektroStudios ElektroStudios added the bug Something isn't working label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant