I'm reading many comments about how to run Studio One 5 R2R on Windows 7.
We know it is not supported anymore and few errors happen when launch the installer.
Missing VCRUNTIME140_1.dll is one of them.

It should fix it but I haven't tried yet:
https://helpx.adobe.com/illustrator/kb/vcruntime-error-on-launch.html

The challenge is to make Studio One 5 R2R working on Windows 7, why not if it is not impossible?

Edit:
Screenshots are welcome (errors, dialogue box, etc)

 

Last edited: Aug 19, 2020

It's going to take more than just making sure your VC Runtimes are up to date.
You'll end up reading about the Universal CRT - see here https://github.com/dotnet/runtime/issues/3930
and given that I haven't practically explored that stuff (yet) I've no idea whether ideas in that thread will actually work.
It won't be a quick fix to explore but maybe possible,
and maybe even simple to do after putting in enough time to explore.
Not high enough on my priority list to look at anytime soon. Good luck.

UPDATE: gave it a quick try.
Got past all the complaints about missing dlls. and then it still won't launch.
For me that means cut my losses and don't waste any more time.
AND, same failure story for the Presonus Hub,
which was actually what I would have liked to see working on W7

 

Last edited: Aug 19, 2020

According to the GitHub page, you're supposed to install the following:

https://download.microsoft.com/down...57E-520D5D138140/Windows6.1-KB2999226-x64.msu

He then gives instructions for extracting files from the .msu, or you can just download a 7zip file of the already extracted files from https://gist.github.com/eladkarako/...-for-windows-7-x86-x64-windows-8-1-x86-x64-md.

But I have no idea what you're supposed to do with the extracted files, or why you would need to extract them at all if you're installing the .msu update.

 

tried a few tricks from the web, none worked for me but i am no computer wiz
gave up. better upgrade my PC altogether it's getting old, first gen i7
OMG the stuff i have to reinstall...

 

That's interesting!
So you passed all missing dll errors but still wont launch.
If we are not too late, is it possible to look at a capture of the last error?

When things become difficult then it is time for fun.

PS. I'm using win10 too but still interested to make it working on win7.

 

Pal, your intention is very good in trying to perform this, but I find it very difficult to work. I already agreed (to myself!): for now, no PSO5 for me, since my W8.1 Pro is working very well, really smooth. But in the next OS installation, I will unfortunately migrate to the W10 Lite [oprekin] 1909,753.
Anyway, good luck in this fight and don't forget to have fun in the process!

 

Oh shit, here we go again...

 

OK, scruffy(ish) details OF A FAILURE. Sorry - would have been tidier if I had succeeded but I failed.

The platform I tested on...
- Windows 7 Ultimate 64-bit
- dotnet 4.8 (that's as high as it gets on W7 - I think)
- Microsoft Visual C++ 2015-2019 Redistributable (x64) 14.25.28508 (and also the x86 version just in case)

I supplemented the dlls following the info at that github link https://github.com/dotnet/runtime/issues/3930
2 batches are available - I tried them both
[1] u..rsalcrt-apifwd-win7_6.1.7601.18972 and ucrt_6.1.7601.18972
[2] u..rsalcrt-apifwd-win7_6.1.7601.23175 and ucrt_6.1.7601.23175

By themselves the above folders of dlls are not enough.
There are subsequent individual dlls that it complains about being missing.
So I added each of these dlls separately following each error
- api-ms-win-core-winrt-l1-1-0.dll
- msvcp_win.dll
- dcomp.dll
- win32u.dll

Eventually it stopped complaining about missing dlls and gave me this error
The procedure entry point__uncaught_exceptions could not be located
in the dynamic link library api-ms-win-crt-private-l1-1-0.dll
(that dll is definitely there)

For me - that was a quickie effort - worth a try - but it failed.
I now recognise a saga that I will not solve easily, so I know when to quit.

I look forward to seeing someone smarter, crazier, luckier, and the bearer of better news - good luck.

 

That's really a lot of stuff, thanks.

Am I wrong to look at here?

http://windowsbulletin.com/files/dll/mozilla/firefox/api-ms-win-crt-private-l1-1-0-dll

api-ms-win-crt-private-l1-1-0.dll

is it the same dll?

we need to ask presonous to link to a static library next time

Does Presonus Hub have the some issues?

 

Try installing this one:

https://www.sereby.org/site/All in One Runtimes&lang=en

And see if it still fails afterward (of course remove all your manually copied DLL files before doing so).

 

Thanks a lot but that's a bit too much for me.

Usually I'm prone to search for cleaner or more elegant solutions.

 

I used to work for Presonus. I have pals on the inside. Some of them wish S15 would run on Win7 too.
But they all told me it can't be done. S15 NEEDS Win10 to run.

 

What's the dependency that's unique to win 10 ??

 

Exactly this ↑↑↑

 

It seems to me that software suppliers are kissing Microsoft's Butt by purposely making changes to their newer programs to hamper, stop or restrict their installation on a Windows 7 PC. I personally have no problems yet as I already have everything I need and they are all working perfectly, hence no need for upgrades, I don't use my music PC online either.

 

It is interesting that reaper supports older os like xp. Dmgaudio too, not supported by old OSes (supports only vista, 7 and higher), but might work on xp and older...

 

Last edited: Aug 20, 2020

Probably some kernel level stuff, if devs are actually saying it's impossible to run on Windows 7.

 

You just need to download the file and run it, so that it can install all the runtimes. No rocket science really.

 

WinRT.
Its a replacement for managed C++ made for Windows 8 and above. The problem won't be solved by simply placing DLLs. Apps can be re-coded to run without using it by using an older technology. more information on Wikipedia
Its a low level detail, so just upgrade to Win10. It isn't as bad as you think.

 

Thanks for the WinRT tips.

Re: W10 advice
I'm not actually disagreeing with your comments about Win 10, and 'occasionally' it might be good advice for some people.

But, in general, it is a dull mistake (that I hear too often, and probably you're not making) to assume that people using W7
are just nervously trying to avoid W10.

I have many platforms using many OS, including XP, W7, W8, W10, and OSX.
I have very good reasons for using all of them, and will eagerly use whatever comes next too.

My W7 configurations will actually never become obsolete. They share space with W10 platforms and whatever W10 morphs into next. Currently W7 platforms still comfortably carry the lion's share of serious music work. There's enough hardware and spares in my workshop to ensure that these music boxes will probably last longer than me. I treat them all like instruments, they worked yesterday, they will work tomorrow. I wouldn't throw an old violin away just because it can't sound like a modern electric guitar.

So, please, politely please, to anyone that makes that mistake,
stop thinking of W7 users as luddites too scared to contemplate W10.
(and I repeat I don't assume @demberto is making that mistake)

Cheers