Solution Report > F/Up from: F 21 Mar 25 Time Now 5:15 Est

I promised to get back to Trebor and Kozikowski. I noticed that post was closed by this system. So, I am opening this post to make good on my promise to get back once the problem was solved. So, I hope this is being categorized properly in this forum; if not, then please forgive me since I do not regularly use this forum.

I am addressing right now: Trebor and Kozikowski.
It took about 3 or 4 days shy of two months for Adobe CC to solve the problem of why I wasn’t able to sign back into my account at Adobe Creative Cloud (All apps). I certainly did not like having to follow their instructions of having to reinstall my Windows 11 in my computer. Yes, it was scary doing that, but I had to trust their troubleshooting steps. The two reinstalls of my Windows 11 did not solve the problem as they predicted it would. Eventually they were taking various logs off of my computer. About a week ago, they finally solved the problem.
It seems to have come down to them replacing a .dll file. Which stands for a dynamic link library file.
I am now able to get back into my Adobe CC account.
Am I a bit pissed at having to lose progress on business projects I was working on while they tried to debug and solve the problem? Yes, I am annoyed. Am I also annoyed about having to rebuild certain icons back onto my computer, as Audacity and others? Yes, I am annoyed. But things had to be done.
Do I appreciate all the help and advise I received from you folks at Audacity, like Trebor and Kozikowski? Yes, I did appreciate learning from what you originally wrote me. Even though a lot of what was said was way over my “head” or understanding.
Look folks, I am glad I am finally back into my Adobe CC account.
I am currently trying to get Adobe to do something for me for the inconvenience they cost me. I pretty much had to stop any progress I was making on other computer projects, because I didn’t know what they were going to do next in troubleshooting the problem. At this point, I am not sure what they are going to do for me, since I am still considered a student of their suite of programs. All I can say right now is: I hope I can work things out with them at Adobe CC.
Now, please understand, I cannot keep up on participating in this thread and conversation. I just have too many things pulling me in different directions for my main business and life circumstances. If something significant develops then perhaps if I have time then I may add another post here. But then again, I may not.
The important thing to tell you folks is this: They replaced a file with a .dll extension. And that solved the problem. But that is just the beginning of the work I have to now do.
With Audacity: I am currently using 3.7.3 and I have no idea how I managed to follow the video directions for installing the FFmpeg file. But I did that too. And I tested to see if I was able to open a saved file on my flashdrive and get it into Audacity and play it. Thank goodness it works.
Well, I kept my promise to you terrific people.

1 Like

That will be this thread I presume: F 21 Mar 25 Time now 5:15 Est - #29 by Tonkda

Thanks for the update. Glad to hear that the problems were eventually resolved.

PC cleaner software like “WinZip System Utilities Suite” is capable of removing references to dll’s.
The moral of the story: never use 3rd party PC cleaner software.