F5F Stay Refreshed Hardware Desktop Each time I launch a game, Steam executes the installscript.vdf file with admin privileges.

Each time I launch a game, Steam executes the installscript.vdf file with admin privileges.

Each time I launch a game, Steam executes the installscript.vdf file with admin privileges.

S
steel51
Member
205
08-29-2021, 10:20 PM
#1
Hey there, I'm trying to figure out what's going on with my Windows 11 Pro setup from September 2025. I'm using the newest 25H2 version with the latest drivers installed. The problem seems to start when Steam launches any game—it tries to run the installscript.vdf file and ends up installing a C++ Redistributable. Then the game starts, but it keeps asking for admin permission every time I boot up games in my library.

I've tried a few fixes: reinstalling specific titles, updating my Steam client, moving the installation folder around, checking file integrity, removing registry keys that Steam thinks are blocked, and even deleting all C++ Redistributables from the CommonRedist folder. But nothing seems to work.

My machine specs are pretty standard—AMD R7 9800X3D, RTX 3090, 32GB T-Create DDR5, Gigabyte B850, and a 2TB Sabrent Rocket NVMe drive. I'm on Windows 11 Pro 64-bit. I'm really struggling with the UAC prompt every time I launch a game, and it's making things super frustrating. Any advice or help would be super welcome.
S
steel51
08-29-2021, 10:20 PM #1

Hey there, I'm trying to figure out what's going on with my Windows 11 Pro setup from September 2025. I'm using the newest 25H2 version with the latest drivers installed. The problem seems to start when Steam launches any game—it tries to run the installscript.vdf file and ends up installing a C++ Redistributable. Then the game starts, but it keeps asking for admin permission every time I boot up games in my library.

I've tried a few fixes: reinstalling specific titles, updating my Steam client, moving the installation folder around, checking file integrity, removing registry keys that Steam thinks are blocked, and even deleting all C++ Redistributables from the CommonRedist folder. But nothing seems to work.

My machine specs are pretty standard—AMD R7 9800X3D, RTX 3090, 32GB T-Create DDR5, Gigabyte B850, and a 2TB Sabrent Rocket NVMe drive. I'm on Windows 11 Pro 64-bit. I'm really struggling with the UAC prompt every time I launch a game, and it's making things super frustrating. Any advice or help would be super welcome.

S
SuperProtoMan
Junior Member
47
08-31-2021, 05:32 PM
#2
It appears to be a typical issue, and a simple search revealed several solutions.
S
SuperProtoMan
08-31-2021, 05:32 PM #2

It appears to be a typical issue, and a simple search revealed several solutions.

L
laime_419
Junior Member
28
08-31-2021, 10:41 PM
#3
I’ve checked numerous Google results and found no permanent remedy. Removing the installscript.vdf file only works temporarily. There must be a deeper issue that needs addressing.
L
laime_419
08-31-2021, 10:41 PM #3

I’ve checked numerous Google results and found no permanent remedy. Removing the installscript.vdf file only works temporarily. There must be a deeper issue that needs addressing.

R
RepoRizer
Posting Freak
872
09-01-2021, 05:19 PM
#4
I fully removed Steam and used Revo Registry Cleaner to eliminate any Steam/Valve-related entries from my registry. I then checked the integrity of all game files in my library. Once completed, the first install script was able to properly assign the correct registry keys and prevent the UAC prompt from showing up. I’m not sure what triggered the problem since I don’t run any registry tools beyond that, and it only happened recently. Still, it’s resolved for now, giving me some peace of mind.
R
RepoRizer
09-01-2021, 05:19 PM #4

I fully removed Steam and used Revo Registry Cleaner to eliminate any Steam/Valve-related entries from my registry. I then checked the integrity of all game files in my library. Once completed, the first install script was able to properly assign the correct registry keys and prevent the UAC prompt from showing up. I’m not sure what triggered the problem since I don’t run any registry tools beyond that, and it only happened recently. Still, it’s resolved for now, giving me some peace of mind.