Hi, as the title says, I reinstalled windows to accommodate new hardware in my PC and now I'm getting all kinds of error messages and crashes. Most of the error messages are related to Live's inability to delete the undo file, or the previous VST scan log, or unable to close the save file of the current project to overwrite it.
I have of course set myself up as the administrator of this PC, I've set Live up to run as administrator, I've changed permissions on the Ableton AppData folder so that not just me or Live, but "Everyone" should be able to overwrite files. And yet, I can't figure out why Ableton can't seem to delete or write to that folder consistently
At one point I got a message that Ableton could erase the VST scan log because it was in use by SYNSOPOS.exe, which is even more bizarre because that's just a part of the eLicenser program and has nothing to do with Ableton whatsoever. I'm not sure how to proceed here. One thing that appears to be part of the problem is that when I click the properties of appdata/Ableton it is set to read only. So I uncheck read only, and then the next time I check its properties - even seconds later - it's read only again.
Edit - I think I may have solved it. Writing the solution here in case anyone ever dig up this thread in search of an answer. The reason AppData/Ableton would not hold its settings when I unchecked Read-Only is because its parent folder, AppData is read only. So I disabled that first, then unchecked Read-Only on the Ableton folder. You have to affirm to apply it to files and subfolders as well. Supposedly windows pretty much ignores a read only setting on folders, but there must be some files in those folders that have been set as read only. Evidently running Live as Administrator isn't sufficient to override that. I've only tested it for a little while so far, but it seems to have resolved. No errors about being unable to overwrite save files or VSTscan logs or undo.cfg. No crash on exit. So far so good. I also deleted my preferences.cfg for good measure. Make sure if you do this you move your template file out of the preferences folder. I had a couple crashes while starting up because Live couldn't locate any of the plugins in my template file, and with my preferences file deleted, it didn't even have a folder to scan, even though my database file was still there.
Edit 2 - the above was a temporary solution it seems. Windows acting stupid again as soon as I restarted. What I've tried since, which has worked so far, is taking Ownership of the files and folders. Some of the project files that I couldn't overwrite were stored on a second hard drive that doesn't even have Windows on it, so it doesn't make much sense that I'd be getting interference from permissions settings, but the Owner of the files on that drive was SYSTEM. Making myself Owner seems to have worked for now
New motherboard and CPU -> new install of windows -> problems with write permissions in Live
New motherboard and CPU -> new install of windows -> problems with write permissions in Live
Win 10 Pro
Ryzen 9 3900XT
UAD Apollo/ART Voice Channel
Ableton Live 10/Cubase 10.5
Push 2/Moog Subsequent 37
Ryzen 9 3900XT
UAD Apollo/ART Voice Channel
Ableton Live 10/Cubase 10.5
Push 2/Moog Subsequent 37
-
ZitstringeR
- Posts: 3
- Joined: Fri Aug 07, 2020 2:45 am
Re: New motherboard and CPU -> new install of windows -> problems with write permissions in Live
Thats because Ableton uses Hardware ID if you changed your Mobo the Hardware id Autherization on your Hard drive is set to your old motherboard your best bet would be backup all your goodlies do a fresh windows install then when you re authorize ableton it will set to your new hardware if it doesnt contact LIVE support ask them to remove your hardware id from their server of your old motherboard but you should be able to authorize afyer a fresh install as your old authorization file would have been deleted in the reinstall of windows or remove ableton live delete from registry in hkeys and software and reinstall but a fresh windows install is always good you say fresh install did you go into custom setup delete all the drives so your c drive say 500gb of 500gb or whatever your drive size is if you used windows to fresh you pc then the HDD wasnt completely wiped