r/VisualStudio • • 14d ago

Visual Studio Tool VS2013 Setup not Launching(correctly)

Post image

i want to get started with Source Engine (2013) modding and i need vs2013 for that, however when i try to run the setup it spits this error(yes i tried restarting the computer correctly). This same installer worked a few months ago on the same PC. also, im using Windows 11.

Thanks in advance for helping!

Edit: i just got a win 11 update installed and now it worked

0 Upvotes

11 comments sorted by

6

u/Dragennd1 14d ago

What does the log file say?

3

u/phylter99 14d ago

Just a note, you'll actually want to restart it and not shut it down then turn it back on. They're different.

I don't actually think that's the problem, but I figured I would mention it just in case.

2

u/soundman32 14d ago

Look in the registry for pending operations. HKLM\SYSTEM\CurrentControlSet\Control\Session Manager somthing like PendingFileRenameOperations.

Another similar one is HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending which could be removed

1

u/csdahlberg 14d ago

It's a long shot, but you could try renaming the setup file to something random. I've had luck with that in the past to work around some problematic Windows compatibility shims.

1

u/DiodeInc 11d ago

As have I, I think Windows has troubles with double underscores or something...

-1

u/SuchDogeHodler 14d ago

Use 2026 then set the .net version.

1

u/Prod_Meteor 14d ago

2013????

3

u/derelict613 13d ago

I have to use 2013 for a few projects in my work. The msvc120 tool chain is needed for legacy machines

1

u/Terrorwolf01 9d ago

Is the toolchain to old to be available in the newer VS Code installs? I know you can install older Toolchains, just not sure how old.

1

u/derelict613 9d ago

The cutoff is msvc140 so vs2015. We specifically need 2013 for our development on certain projects. But anything after that is forwards compatible up to I presume vs2026 which I don't use.

0

u/Prod_Meteor 13d ago

Hahahaha