Hi,
Has anyone installed sforzando 1.980 on a Windows 7 x64 DAW?
The download says Win 10 minimum, the user guide says Win 7 is ok.
I'm wondering if this is just a case of "no more support for Win 7" and am trying to learn if/when/what version will not work in Win 7.
Thank you.
sforzando 1.980 on old Windows 7 DAW?
-
- KVRist
- 178 posts since 24 Jun, 2013
-
- KVRist
- Topic Starter
- 178 posts since 24 Jun, 2013
Hi,
It's me again.
I just tried the install, and everything seemed to go great.
When I launched my DAW, REAPER, a dialog about the new DLL files popped up and said there was a problem.
I tried the standalone player and had the same problem.
So, I guess the answer is no, v 1.980 will not work on Win7.
I looked at the changelogs and do not see any notes indicating the last version that would work with Windows 7. I also have not found any legacy installers made available by Plogue, although many seem to be available on sketchy sites.
Anyways... I hope the info helps someone else.
I used a disk image to clean my system and return to the future.
Thank you.
It's me again.
I just tried the install, and everything seemed to go great.
When I launched my DAW, REAPER, a dialog about the new DLL files popped up and said there was a problem.
I tried the standalone player and had the same problem.
So, I guess the answer is no, v 1.980 will not work on Win7.
I looked at the changelogs and do not see any notes indicating the last version that would work with Windows 7. I also have not found any legacy installers made available by Plogue, although many seem to be available on sketchy sites.
Anyways... I hope the info helps someone else.
I used a disk image to clean my system and return to the future.
Thank you.
-
- KVRian
- 1112 posts since 20 Oct, 2018
https://plugins4free.com/plugin/1371/
It's an earlier version. Hopefully good for win7.
It's an earlier version. Hopefully good for win7.
-
- KVRian
- 769 posts since 18 Nov, 2008
Works fine for me on Windows 7 64 bit.
I had 1.977 installed and that one worked.
Uninstalled 1.977 and then installed 1.980 and still works without a problem.
I feared that 1.980 would not work when I read:
* Preliminary native Windows 11 ARM64 build
in the changelog for v1.980 May 22nd 2025
But luckily, no problem at all.
Standalone as well as CLAP, VST3 and VST (64 and 32 bit) all work well.
So maybe a more detailed info about what error you get exactly might help?
I had 1.977 installed and that one worked.
Uninstalled 1.977 and then installed 1.980 and still works without a problem.
I feared that 1.980 would not work when I read:
* Preliminary native Windows 11 ARM64 build
in the changelog for v1.980 May 22nd 2025
But luckily, no problem at all.
Standalone as well as CLAP, VST3 and VST (64 and 32 bit) all work well.
So maybe a more detailed info about what error you get exactly might help?
-
- KVRian
- 519 posts since 20 Dec, 2008
Internet Archive is your friend. For example, the v1.625 installer was archived with the site on March 2nd, 2013. On that date the Windows system requirements were "PC: Windows XP® or higher".
-
- KVRist
- Topic Starter
- 178 posts since 24 Jun, 2013
Hi everyone,
Thank you for all the encouraging information.
I tried a copy of 1.977 earlier today, and it works fine on my Windows 7 machine.
I don't remember the exact wording of the error dialog, it identified a .dll file that was a problem. I used a backup disk image to restore the OS to a previous state, so it is too late to figure it out now.
I will stick with 1.977 for now.
Thank you!
Thank you for all the encouraging information.
I tried a copy of 1.977 earlier today, and it works fine on my Windows 7 machine.
I don't remember the exact wording of the error dialog, it identified a .dll file that was a problem. I used a backup disk image to restore the OS to a previous state, so it is too late to figure it out now.
I will stick with 1.977 for now.
Thank you!
-
- KVRian
- 928 posts since 3 Aug, 2001 from Montreal
Pardon my French:
Had to boot up my wife's old laptop (after reconnecting the discarded HD and all, fun stuff).
1.980 very much works here on final W7 x64 with SP1+"Platform Update" (for D2D).
I was afraid that somehow the MSVC2022 C/C++ runtimes had somehow changed but its not the case. As you do not remember what the message was I'm not 100% on that but...
It is MOST probably due to our DRM requiring valid _semi recent_ root certificates to be installed. But that requires internet access. I assume you turned that off (rightfully in 2025).
We previously shipped with root certs in the installer but might not have done it lately. Note: you do not have to use a browser for this. Its really native windows services that does this as soon as windows native DRM services run. Once it ran (and sforzando started, you can then disable internet drivers - its really a one time thing)
The next version of sforzando (1.981) on Windows will require yet another certificate so might as well remove the W7 compatibility altogether.
A quick note on my personal philosophy regarding older machines. I am very much aligned with rights to repair, perma-computing and generally being able to run software on older hardware for as long as it is technically possible. That however stops at older OSes that are not supported by their makers. This is VERY dangerous. If your machine ran W7 x64, it surely will be able to run W8.1 possibly W10 too. But as both of these will be out of support we just came up with NATIVE Linux versions (see our forums). I can run the x86-64 and aarch64 (arm64) builds of sforzando on a bunch of e-waste bound machines that I've collected here for tests and those have nearly daily security updates
Cheers
1.980 very much works here on final W7 x64 with SP1+"Platform Update" (for D2D).
I was afraid that somehow the MSVC2022 C/C++ runtimes had somehow changed but its not the case. As you do not remember what the message was I'm not 100% on that but...
It is MOST probably due to our DRM requiring valid _semi recent_ root certificates to be installed. But that requires internet access. I assume you turned that off (rightfully in 2025).
We previously shipped with root certs in the installer but might not have done it lately. Note: you do not have to use a browser for this. Its really native windows services that does this as soon as windows native DRM services run. Once it ran (and sforzando started, you can then disable internet drivers - its really a one time thing)
The next version of sforzando (1.981) on Windows will require yet another certificate so might as well remove the W7 compatibility altogether.
A quick note on my personal philosophy regarding older machines. I am very much aligned with rights to repair, perma-computing and generally being able to run software on older hardware for as long as it is technically possible. That however stops at older OSes that are not supported by their makers. This is VERY dangerous. If your machine ran W7 x64, it surely will be able to run W8.1 possibly W10 too. But as both of these will be out of support we just came up with NATIVE Linux versions (see our forums). I can run the x86-64 and aarch64 (arm64) builds of sforzando on a bunch of e-waste bound machines that I've collected here for tests and those have nearly daily security updates
Cheers
You do not have the required permissions to view the files attached to this post.
David Viens, Plogue Art et Technologie Inc. Montreal.
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
-
- KVRist
- Topic Starter
- 178 posts since 24 Jun, 2013
Hi,
Thank you for taking a look at this thread and offering your insights.
FWIW, I run a circa 2013 DAW using Win 7 x64 that was last on the internet, if it ever was, when it was assembled and the OS was activated. It has been offline 100% of the time I have owned and used it in my offline studio.
It works great, has 24 high-quality audio I/O, and has almost no round-trip latency.
I have disk image backups for occasions when I regret installing something and want to restore the entire image to a previous happy state.
I am writing this post on a 1-month-old custom-built, overclocked Win 11 AMD 9950X Nvidia 5070 96GB DDR 6400 machine that I use for graphics, web, etc. It gets mystery meat updates daily and acts weird when kowtowing before its cloud-based overlords.
Being happy and satisfied with my 100% offline DAW does not feel nearly as dangerous.
Thank you!
Thank you for taking a look at this thread and offering your insights.
FWIW, I run a circa 2013 DAW using Win 7 x64 that was last on the internet, if it ever was, when it was assembled and the OS was activated. It has been offline 100% of the time I have owned and used it in my offline studio.
It works great, has 24 high-quality audio I/O, and has almost no round-trip latency.
I have disk image backups for occasions when I regret installing something and want to restore the entire image to a previous happy state.
I am writing this post on a 1-month-old custom-built, overclocked Win 11 AMD 9950X Nvidia 5070 96GB DDR 6400 machine that I use for graphics, web, etc. It gets mystery meat updates daily and acts weird when kowtowing before its cloud-based overlords.
Being happy and satisfied with my 100% offline DAW does not feel nearly as dangerous.
Thank you!