Steam Directory/Folder/File "Locked"-Unable to Delete Files-Requires Admin Permission/Access Denied

[TeutonTiberius]

For whatever reason, my Steam folder, directory, or whatever term you want to use, is practically "locked." By that, I mean that my folder requires administrator approval to delete files; despite my account being the administrator.

Does this pertain to installing files? Well, I couldn't tell you. That said, I recently installed Skyrim SE only for Steam to say it wasn't installed (upon rebooting the PC). After reboot, I hit the "Install" button again and only then did it pick up the Skyrim SE folder's presence. I also had an issue with a The Witcher 3 mod (Better Than Icons) where I was required to reinstall the mod in Safe Mode, but that's beside the point.

I've since reinstalled my OS (twice) deleted and reinstalled Steam (thrice-using Safe Mode), and
all but given up hope. The problem always comes back.

I've read other Forum threads to no avail. One person suggested that it was that Steam should be installed to a directory outside of program files, as to avoid User Account Control. So, I installed it to "C:/Games" only for my Steam folder to "lock up" again. Others say to exempt the folder from Windows Defender. So, I tried that too.

Still, I have this issue where files within the Steam folder are undeletable outside of Safe Mode. Installing mods is now an incredibly unstable process as certain fils are unaccessable ("access denied"). I think it might be a background process, but I'm unsure what kind of background process could possibly cause this issue. It's also possible that Steam, itself, is doing this. As a modder this is practically the bane of my existance. Please help. :(

~TeutonTiberius~

Solution Found:
Turns out it's an Intel UI graphics technology issue. igfxEM.exe is one executable causing the issue. It's a component of Intel's Common User Interface (igfxCUIservice.exe), which is a standard Intel installation package provided when installing Microsoft Windows.

The solution? Open task manager and end any process under the "Details" tab that is prefixed by "igfx". So anything along the lines of "igfxEM.exe" or "igfxCUIService.exe".

For whatever reason Common User Interface is notorious for locking files that are accessed when booting up games; so practically any Steam, Blizzard, or Origin game folder (or any other game app for that matter).

[TeutonTiberius]

Any help?

[Lucia]

This was posted a while ago but it's also an ongoing issue for me as well. Steam locks the folder/file from being deleted. The only way to delete it is in safe mode which is ridiculous to do over and over again.

[TeutonTiberius]

Paranoiac eredeti hozzászólása:

This was posted a while ago but it's also an ongoing issue for me as well. Steam locks the folder/file from being deleted. The only way to delete it is in safe mode which is ridiculous to do over and over again.

Turns out it's an Intel UI graphics technology issue. igfxEM.exe is one executable causing the issue. It's a component of Intel's Common User Interface (igfxCUIservice.exe), which is a standard Intel installation package provided when installing Microsoft Windows.

The solution? Open task manager and end any process under the "Details" tab that is prefixed by "igfx". So anything along the lines of "igfxEM.exe" or "igfxCUIService.exe".

For whatever reason Common User Interface is notorious for locking files that are accessed when booting up games; so practically any Steam, Blizzard, or Origin game folder (or any other game app for that matter).

Hope this helps.

[Lucia]

TeutonTiberius eredeti hozzászólása:

Paranoiac eredeti hozzászólása:

This was posted a while ago but it's also an ongoing issue for me as well. Steam locks the folder/file from being deleted. The only way to delete it is in safe mode which is ridiculous to do over and over again.

Turns out it's an Intel UI graphics technology issue. igfxEM.exe is one, it's a component of Intel's Common User Interface (igfxCUIservice.exe), which is a standard Intel installation package provided when installing Microsoft Windows.

"If igfxCUIService.exe is located in a subfolder of C:\, the security rating is 64% dangerous."
~File.net

The solution? Open task manager and end any process under the "Details" tab that is prefixed by "igfx". So anything along the lines of "igfxEM.exe" or "igfxCUIService.exe".

For whatever reason Common User Interface is notorious for locking files that are accessed when booting up games; so practically any Steam, Blizzard, or Origin game folder (or any other game app for that matter).

Hope this helps.

Thanks dude, you're a legend

[Seven7]

real igfxCUIService.exe igfxEM.exe NEVER can be in C:\intel, etc
in c:\windows\system32\driverstore\ ONLY
it's just a trojan

[TeutonTiberius]

Seven7 eredeti hozzászólása:

real igfxCUIService.exe igfxEM.exe NEVER can be in C:\intel, etc
in c:\windows\system32\driverstore\ ONLY
it's just a trojan :sadelf:

You're right; just quoted File.net. Didn't really think about it.

[TeutonTiberius]

Paranoiac eredeti hozzászólása:

TeutonTiberius eredeti hozzászólása:

Turns out it's an Intel UI graphics technology issue. igfxEM.exe is one, it's a component of Intel's Common User Interface (igfxCUIservice.exe), which is a standard Intel installation package provided when installing Microsoft Windows.

"If igfxCUIService.exe is located in a subfolder of C:\, the security rating is 64% dangerous."
~File.net

The solution? Open task manager and end any process under the "Details" tab that is prefixed by "igfx". So anything along the lines of "igfxEM.exe" or "igfxCUIService.exe".

For whatever reason Common User Interface is notorious for locking files that are accessed when booting up games; so practically any Steam, Blizzard, or Origin game folder (or any other game app for that matter).

Hope this helps.

Thanks dude, you're a legend :msfortune:

Welcome :D

[Seven7]

Now it convert into urban legend: many users think that Intel HD have problems with Steam client \ games... make videos, distribute tips how to break IntelHD driver to solve the problem, instead of searching for the real reason

[OBNOXIUs]

thanks for the solution