[Bug]: 'Disable Nvidia telemetry drivers': Access to the path is denied

[ElektroStudios]

Description

The following script with description:

• --- Disable Nvidia telemetry drivers

Is causing the following error messages:

Failed to rename "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\NvTelemetry64.dll"

to "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\NvTelemetry64.dll.OLD":

Access to the path is denied.

• CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
• FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException

I think the script logic is wrong, as it should first try to take ownership of the directory... in my case it wouldn't have issues for doing so. And after privileges are acquired then rename the file, or warn if privileges are not properly acquired, instead of provoking this exception.

That is how I solved it: Manually taking ownership of the folder, then manually renaming the affected DLL file. Ensuring ownership I think is something the script should handle automatically.

I've also noticed that other scripts are also trying to rename or delete files inside the Windows folder before first acquiring ownership... like for example those scripts that clears *.etl log files inside C:\Windows\Logs\waasmedic

I really think acquiring ownership should be a default integrated and controlled mechanism in every script.

---

Partial output (in Spanish):

sexy_NvidiaTelemetry.txt

---

How can the bug be recreated?

I'm pretty sure this error will occur to everybody just by executing that script, since by default that folder populated by nVidia drivers will not have acquired user ownership.

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

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