No way to un-install Beta

[Wienke]

I am not interested in being an unpaid beta tester for Adobe.

So when I found Creative Cloud Desktop launching straight to Beta, I checked Help for how to get out. It said to use the three dots for More on Beta Apps and there would be an uninstall option.

Never minding that I should not have had to look this up in the first place:

1) There is no three-dots icon for all beta apps together; you would have to take this step for each individual app, and not all of them even have a three-dots icon.

2) The three-dots icon actually does not lead you to an uninstall option. So I'm just stuck.

Thanks but no thanks, Adobe. Beta should be an opt-in, not a matter of coercion.

[kglad]

i've never had any app install without my selecting it be installed.

what app (beta or otherwise) installed without you actively opting to install it?

[Wienke]

Creative Cloud Desktop itself is what installed Beta on its own. Today it launched to a Home screen with a Beta badge at the top left.

Looking at Creative Clouds Apps > Beta Apps section again, I see that the action button for those is "Install." I didn't notice that because my focus was on following the instructions to un-install Creative Cloud Beta itself.

So I can get to the All Apps section with one mouse click--which apparently now I must do every time Creative Cloud launches (it causes problems if I leave it running all the time). That's a small annoyance, nothing compared to the periodic and probably not entirely necessary annoyance of having to wait a long time for updates to launch. But I really could have done without the extra Beta puzzle from Creative Cloud this morning.

Thanks, kglad, for your answer.

[kglad]

so, is your cc working, perhaps not perfectly, but acceptably?

[Wienke]

It is. Thanks again.

[kglad]

ok. hope it stays that way, otherwise post again.

[Svein_Skogen]

The added antisocial networking "home" spamtab eats cpu and gpu resources. But I suspect that satisfies Adobe quite well, and is the intent of adding yet more bloat to the software they force on all their paying customers along with the "Genuine Disadvantage" spyware.

Personally I think any company installing beta-grade software without explicit permission on their customer's computers should have their board of directors jailed, but that's just my subjective feeling on the matter.

[Svein_Skogen]

I understand why you want the new home thingy to spam your preferred "news" and other such things that are yeat another notch on the thumbscrews attached to your customers, but right now the forced-on-us beta eats cpu resources faster than a politician can spend money.

Let me rephrase: The current "let's add antisocial networking here too" garbage that replaced the creative cloud app, makes it even more likely that I start to actively look for replacements for all adobe apps and STOP handing you money than all the other fiascos over the past years combined. It's bad enough that you force us to have your "genuine disadvantage" spyware installed to use the software we are paying for. But adding the cpu and gpu load of a refreshing web feed, just so you can add more spam and spyware speaks of a disrespect for your customers that even breaks YOUR scale.

Shame on you, Adobe!

[FGC2]

It definitely locked up the boot process on a MacBook Air using MacOS Monterey 12.6.4 and i did not request it, or agree to use the BETA (BUGGY) Version of the Desktop Creative Cloud app that i've been using since September 2012.  Interesting,  I did not check the "autoload" with startup, and it attempted to load during startup and locked up the boot process where i needed to do a power down, disconnect the dock, then reboot and log in again before using it.  I'm not very happy! 

[Svein_Skogen]

On windows, luckily, it doesn't "lock up", it just ... slows everything down. When a top-spec Surface Studio Laptop (i7/32G/A2000/2T) becomes nearly unusable because Adobe decides to force-feed a beta without asking, it's seriously time to consider the value-for-money on using Adobe as a supplier of productivity software. Because of the lost productivity...

[kglad]

if either of you, @Svein_Skogen or @FGC2 want help, start another thread.

[Svein_Skogen]

From experience - What happens when people start a thread here, is that someone (usually tagged "expert") adds "This is as intented", then their friend marks that as "the correct answer" and the post is forgotten. Usually without actually solving the problem. Case in point - this thread. User was asking how to remove an unwanted beta, YOU simply asked if it was working at all, and flagged that as the correct answer. No solution to removing the beta was provided, yet you flagged the useless answer as correct.

Pretty much proving that starting a thread here is useless. I'm guessing the reason you're asking for that, is that you don't want notification mails that people are still discussing something you hoped was closed and forgotten, right?

[kglad]

@Svein_Skogen 

i marked nothing correct. but i would be surprised if you acknowledged your error without a "yes, but..."

[Svein_Skogen]

It's fully possible YOU weren't the one who marked this as "solved" and your question to the OP as "the solution". But it's a repeating trend on this forum that everything critical of Adobe changes or Adobe abuses of auto updates and installs, is marked as solved without actually being solved. Perhaps you should take a step back from your "community expert" role, and try thinking "how does this look for a user" and browse the forum a little?

[Wienke]

I’m the one who marked the “correct answer,” but the post I marked was the one expressing doubt that a beta had installed automatically: “i've never had any app install without my selecting it be installed…”

That itself was a solution of sorts because it led me to doublecheck the uninstall instructions and realize that they had been referring to the individual apps, such as Photoshop, not to Creative Cloud Desktop itself.

The implication, then, was that the CC “Beta” badge was just a badly designed invitation to download the individual betas—though I see from subsequent posts that that is not quite true.

FGC2’s posts are actually more helpful, but those solutions are apparently for an older version of MacOS. I’m on MacOS Ventura, and I tried running TQCacheCleaner (the only CC cleaner util), followed by the installer (which wouldn’t launch), so instead the uninstaller (which wouldn’t uninstall CC without first uninstalling Photoshop etc, which I did not want to do), and then the uninstaller’s repair (which redownloads CC), followed by a cold reboot. The only effect of all that was to bring up a CC notification even though I had it set to Off. The CC Home Beta is still there.

I don’t want to miss an update with security implications, but my inclination now is simply to launch Photoshop etc individually and run CC Desktop only periodically.

[FGC2]

I contacted Adobe Support and was told to use the Creative Cloud Cleaner Tool and then use the CC Desktop App Installer to remove the Beta version.

So I tried it and when reinstalled the BETA was still activated. Serious BUG no doubt... Broken from the latest update. I left the request and info with them and they will see if the product development team can fix it. I'll try it without the  DELL D6000 dock installed, and maybe it would allow the boot process to complete. But as for right now nothing wlse is installed besides the CC Desktop App.. No others features of the Creative Cloud Platform will be installed until the bug has been fixed for MacOS Monterey 12.6.4

[FGC2]

After a cold reboot for the macOS Monterey 12.6.4 it now appears to have been resolved after the procedures that were mentioned to Clean and Reinstall the CC Desktop App.  Tried it with restart and then with reboot from a cold start and it does seem to work with my MacBook Air.

But having the Beta version without wanting it seems to be the key issue going forward.

I contacted Adobe Support and was told to use the Creative Cloud Cleaner Tool and then use the CC Desktop App Installer to remove the Beta version.

So I tried it and when reinstalled the BETA was still activated. Serious BUG no doubt... Broken from the latest update. I left the request and info with them and they will see if the product development team can fix it. I'll try it without the  DELL D6000 dock installed, and maybe it would allow the boot process to complete. But as for right now nothing wlse is installed besides the CC Desktop App.. No others features of the Creative Cloud Platform will be installed until the bug has been fixed for MacOS Monterey 12.6.4

By @FGC2

[FGC2]

Today, I updated the DELL D6000 Universal Dock Firmware and Display Manager Application. I'm now able to cold boot the MacBook Air and login with an external display after I set the Dock Display Manager to allow automatic login. The issue here is with the Home (Beta) Tab which still shows up after the reinstall. Setting the Preference, "Launch Creative Cloud to Automatic Login" was set to off. But after reboot the laptop it still allows the Creative Cloud App to Auto login, even though I had turned that setting to off. So the persistence of the auto login option seems to be causing the resources during the boot process to possibly get too low, and I also noticed that downloads for an app take longer than before. But I managed to get around that by turning off the macOS Setting in the Privacy and Security Panel for Allowing Automatic Logout after a specific amount of time. Otherwise the selected CC Apps would not be fully downloaded and I'd have to start the process all over after I logged in again. Before all of this, I first ensured that I was using the latest version, in this case for macOS 12.6.4 Monterey, Build 21G526; Its interesting to note the About Creative Cloud indicates that I'm using Version 5.10.0.573 which is the current version. So I'm assuming the Home (Beta) tab addition is where the problem first showed up for me.

[FGC2]

Heres what I found inside of the D6000 User Guide;

Not enough system resources exist to complete the requested service...

This can occur when entering extend mode with low system resources. The PC does not have enough memory to start an extend display. Close down any unused applications. The situation may also be improved by rebooting the PC;

So the New Home (Beta) tab was initially taking up too much resources to allow the loading of the Dock Drivers which enable the External Monitor to be used.  I have enough memory 8 GB 1600 MHz DDR3... and a 5th Generation Dual-Core Intel Core i7 CPU 5650U used with this laptop MacBookAir (7,2); The Windows 10 laptop using the CCD 5.10.0.573  does not have a Home (Beta) Tab visible. It just shows up as a Home Tab.The macOS is where the Home (Beta) Tab is being pushed.

 I'm now wondering, Is it because an Adobe Software developement team member had forgotten to remove the Beta tag from the Home Tab before it was released?

By @FGC2

[Svein_Skogen]

That kind of actually makes sense, and if so I suspect it is ram related (which explains why it makes a lot harder impact on my laptop than my workstation, and an INSANE impact on your machine with only 8GB ram

My laptop is a Surface Studio Laptop with 32GB ram and is hit rather hard. My workstation has 128GB and the impact is less severe.

I wonder what the memory requirements of this insanity is during loading.

But it also points to my main complaint - that this is bloat at its worst.

Given Adobe's obvious lack of respect for their customers (forcing them as unpaid betatesters without asking), and obvious lack of any real programming skills (visible in this case with the stunning amounts of bloat), and their ego bloating on level with their footprint and their bills, it surely is time to look for alternatives. Good thing Capture One noe lets me do more and more editing without resorting to Photoshop. Perhaps I'll soon be in a position to tell Adobe to deflate their bloat by one customer.

[FGC2]

Well that was quick... I'm no longer seeing the Home (Beta) Tab... It's now the same with either a Windows or a Mac Laptop.  Maybe it was an overlooked error?  I still need to see if they fixed the boot "Auto Login" feature that I was trying to disable before without much success.

[FGC2]

I was able to disable the Creative Cloud Desktop from automatic login by navigating to the Systems Preference / Users & Groups and selecting the Login Items tab. I then deleted the Creative Cloud Desktop Application from the displayed list. It no longer interferes with the cold boot process and saves some resources while starting up. 

[Svein_Skogen]

Alas, that's a mac-specific workaround.

[jane-e]

I am not interested in being an unpaid beta tester for Adobe.

So when I found Creative Cloud Desktop launching straight to Beta, I checked Help for how to get out.

By @Wienke

Hi Wienke,

I saw something about this in a back area when another expert asked about it. Apparently the word "beta" was added to the Creative Cloud app, but it was never in beta and the word was removed by staff. It did not apply to any apps (or even to the CC app).

I'm not sure that I 100% understand it, but you never had a beta version and the word "beta" was removed by the folks who put it there.

I hope that helps!

Jane

[Wienke]

Thanks, Jane-e.

Yes, they have removed the "beta" label, and it was indeed sounding like some sort of mistake, although apparently the "beta" label was not the only mistake, judging by serious problems that other users are having with this new version/update of Creative Cloud.

Frankly, I don't see the point of the Creative Cloud launcher, other than to get updates, and hopefully those will happen on their own since I've chosen the automatic option. And I'm rather unhappy to learn, through all this hubbub, that, even when I have no Adobe product at all running, Creative Cloud is running anyway, and is eating into my CPU/memory resources.

So, one small problem solved, another big problem brewing for the future.