Trouble running addmusick

I am trying to run amk 1.0.10, a week ago addmusick 1.0.8 was running fine.
I updated windows 10 with the recent updates it forced recommended this week.
After that amk keeps giving me this error as shown here:
For the author who made this app, please help out!

Apologies for not getting back to you sooner... mostly because I myself am usually on a Mac, and tend to be blind to the Windows side of things, especially through AMKGUI (though yes, these days someone did port the thing over to the Mac, albeit not using C-Sharp, so I kind of have it on my side). A few things are running through my head, and at least one of them is something that perhaps I can tackle on my end.

• I noticed you had a bunch of blank slots in your local songs list... namely, I don't see anything in there at all. This is a curiosity of mine...
• Try it again with Autoplay SPC not checked? Not sure if that's malfunctioning on your end when calling up a SPC player
• If the song itself has a fault in it... then I don't recognize the text file at all. I'm currently leaning against this case, but you never know...

The reason why I removed the rest of my music slots, none of it would insert not even the one shown in the screenshot.
(all of this suddenly happen in april with a windows 10 update to microsoft framework update)
Addmusick 1.0.8 and 1.0.10 just closes out automatically with no clear description of an error, just chokes out and crashes.
The addmusic gui is the closet thing that describes what might be wrong, my system memory is not an issue and have plenty to spare.

I tried googling the issue and someone said it might be this:
https://www.google.com/search?q=unexception+caught+c%2B%2B+bad+allocation+error&oq=unexception+caught+c%2B%2B+bad+allocation+error&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBCjQwNTQ0ajBqMTWoAgiwAgE&sourceid=chrome&ie=UTF-8
Somebody else on reddit had a very similiar problem to mine a few years ago and never solved it.

...your Google results are probably not the same as mine. Do you have a non-Google (and non-search engine) link to the topic that contained the issue that you had previously located?

I will apologize in advance as I am indeed blind to the Windows side of things, and currently this sounds like it.

Affecting both 1.0.8 and 1.0.10, though... means this isn't isolated to the latest ones. So I'm wondering what's going on that could be causing memory allocation problems... for certain kinds of command line applications, as what seems to be happening here, since the GUI booted up correctly, but apparently not the command line part.

Well neither addmusic is reading my list.txt, just like I have one song in the list, it is having problems reading one single song starting at 40.txt.
Have you ran into a problem like this on the windows command line version ?

I don't really recall, mostly because I've been doing all of my stuff on the Mac (Catalina at that) and not Windows (I don't really use Windows all that often, if at all). Atari 2.0 made some contributions and helped me set up an automated build system so that I could do these builds for Windows (Visual Studio was also upgraded in the process, and they were built through Appveyor). I have a makefile (initially adapted from HertzDevil's fork of AddmusicK, but customized by me) for the non-Windows cases that I use for building.

Actually, from what you're telling me... it sounds like there is some sort of filesystem issue going on with regards to the program being permitted to read a file. Could be wrong.

Please close my topic down I'll finally fixed my problem.

Wonder what happened? Not sure if it was a file permission issue or something else, but glad to see the issue is resolved.