Idk if this was an exception or if I did something wrong on my system but since 6.08 I had constantly errors when trying to install new version on my computer...
Background is probably that I never except a Windows installation like it is... I am changing folder properties to be able to modify them, am moving storage space heavy folders to other places (connecting them with sym-links) to keep the system disk as clean and small as possible...
All of these changes have had absolutely no negative side effects before... just with .msi installers they suddenly started to make trouble...
I researched a bit and was astounished how many complaints one finds over the internet of people where msi fails for a huge range of different reasons... I think the term "Microsoft" already explains a lot...
Now it happened to me with Bitwig installers and msi installers in general...
Did you have had any problems in the past?
I am asking because I requested at support to overthink this ".msi -only" policy and if possible to provide a normal exe installer like all other (DAW) companies are doing... I am not aware of any other going this (dangerous?) .msi way...
What do you think??
Do you have sometimes problems installing/updating Bitwig on Windows because of the .msi installer format?
-
- KVRian
- 1049 posts since 17 Mar, 2005 from Bay Area
Win store is stripped out of my system, so I dont worry too much about it. I manage custom folder structures for all DAWs, all library locations, and Ive never needed to go as far as a symlink to do this. Any content, music, VST location can be changed without the need for a symlink, and so can the core application.
One time, about 6 months ago when BWS beta 6 version 1, or something, came out, they switched to an MSI with some sort of windows app store integration, and I had trouble with that, including BWS refusing to install (please insert disk with blah dot msi on it, etc), but then later they apologized and removed that integration. Ive used latest BWS on a win10 and win11 box using the current MSI without any trouble, as well as mapped custom folders for pretty much everything.
Do you mean you installed content locations on network attached? If so, that might have needed a symlink, but I dont typically do that because my existing setup is faster, more reliable.
One time, about 6 months ago when BWS beta 6 version 1, or something, came out, they switched to an MSI with some sort of windows app store integration, and I had trouble with that, including BWS refusing to install (please insert disk with blah dot msi on it, etc), but then later they apologized and removed that integration. Ive used latest BWS on a win10 and win11 box using the current MSI without any trouble, as well as mapped custom folders for pretty much everything.
Do you mean you installed content locations on network attached? If so, that might have needed a symlink, but I dont typically do that because my existing setup is faster, more reliable.
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
The intention of using sym links is just to keep any for the OS irrelevant data off of the system drive...Milkman wrote: Wed Jun 24, 2026 10:43 pm Win store is stripped out of my system, so I dont worry too much about it. I manage custom folder structures for all DAWs, all library locations, and Ive never needed to go as far as a symlink to do this. Any content, music, VST location can be changed without the need for a symlink, and so can the core application.
I am always working with the older Windows7 Save and restore disk image method, have multiple for different states of my system and when I need to "reset" something to a certain state it´s a matter of probably 5 minutes as my disk image of the C:/ drive are at max about 25gigs in size
Exactly this I haven´t had with any early version but with 6.09!!One time, about 6 months ago when BWS beta 6 version 1, or something, came out, they switched to an MSI with some sort of windows app store integration, and I had trouble with that, including BWS refusing to install (please insert disk with blah dot msi on it, etc), but then later they apologized and removed that integration. Ive used latest BWS on a win10 and win11 box using the current MSI without any trouble, as well as mapped custom folders for pretty much everything.
I had with 6.08 an access error because of the "Windows/Installer" folder I have had outsourced...
6.09 wanted to urgently have access to the 6.08 installer to be able to clean up the previous installation
6.010 made me happy again with another access error...
Every day something new...
No, no network at all here... I like "speed"Do you mean you installed content locations on network attached? If so, that might have needed a symlink, but I dont typically do that because my existing setup is faster, more reliable.
But to be honest I don´t know about other ways to outsource i.e. the VST3 folder to a different drive which needs to be default for some progs like Melodyne in some DAWs and i.e. FL Studio refuses to accept a different location than the default one...
I really need to point out that all my measures have worked fine for at least the last 15 years and still do for every other programm...
Running Bitwig isn´t a problem at all... no crashes... nada...
Just installing msi gives me hard times... (F**ck Microsoft!
)