I get on here to report a bug and get tech help, and am censored by the forum on my first post!
Obviously devs want to bury their heads in the sand by not allowing my post about a LEGIT ERROR MESSAGE!
SEE THE ATTACHMENT FOOLS! THIS IS LEGIT ERROR I AM NOT A SPAMMER - STOP TREATING ME LIKE ONE!!!
HOW CAN ANYONE GET HELP IF ALL THEIR POSTS ARE AUTOCENSORED?!??!?!
All new posters get moderated (not “autocensored”) until you get trusted - otherwise there would be a flood of Spam - same of it nasty and some downright dangerous with seriously iffy payloads. We work hard to keep this corner of the Internet a family-friendly happy place.
The problem you report is a known one - it is not actually an Audacity - it s a shortcoming in your Windows environment.
See this bug report and particularly the workaround: https://bugzilla.audacityteam.org/show_bug.cgi?id=1989
WC
Oh the problem is with MY computer not YOUR software huh?
Strange how my computer runs every single program, including multiple audio related ones (inc. ffmpeg) without ANY ERRORS WHATSOEVER but, of course, this is NOT an audacity problem, oh no. Audacity works fine and EVERY OTHER program on my computer is messed up because it DOES NOT give a cryptic error message when they start up.
Sounds legit. Thanks for clearing that up.
I had this issue as well and there was never an issue with my PC before. This is a known issue though and if you follow the instructions it fairly simple to resolve.
EZ
Relevant forum thread here … https://forum.audacityteam.org/t/audacity-2-3-0-will-not-launch-in-windows-vista-solved/50417/1
Yeah, this is merely issue of Windows, not Audacity. It is not fault of Audacity it requires a system component that’s missing. READ ERROR MESSAGES CAREFULLY! That way you’ll find out that the solution is more simple than you think. A simple Google Search will 100% help you with this issue, and believe it or not, almost all Windows system components can be downloaded for free. This is clearly Visual Studio Tools redistributable component (.NET Framework component to be exact). Reinstalling .NET Framework and Visual Studio x86 and x64 redistributables will fix this issue.