- Creative Cloud Desktop application for Windows: window became blank white and doesn’t show any apps nor anything.
- Looks like it’s working beside the blank window. Notifications like “update available” are shown normally.
Me "Don't be reserved. Which one? (Doubleclicking #CreativeCloud)"
— Romly@技術書典7 せ44D (@Romly) August 18, 2019
I’ve encountered this symptom time to time since quite before. (since the Creative Cloud Desktop application was born) I did troubleshoot each time but this time was tough.
- Relaunching Creative Cloud Desktop app. Restart PC. (just in case)
C:\Users\<user_name>\AppData\Local\Adobe\AAMUpdater(it can be found often by googling.)
C:\Users\<user_name>\AppData\Local\Adobe\OOBE\opm.dbAlso tried renaming the OOBE folder.
- Changing Name/Family Name at adobe.com. (They say that special characters in those field can be cause of error.) But I have no special characters so it changes nothing.
- Over-install Creative Cloud Desktop app. (since I couldn’t uninstall it)
- Delete all files in
In conclusion, uninstall the Creative Cloud Desktop app and installing again fixes the problem. Creative Cloud Desktop app can’t be uninstalled through Control Panel by an error something like “Applications which requires this app still exist on this computer”, so we have to use the uninstall tool.
Direct link for Creative Cloud Uninstaller below, just in case.
Uninstalling process took a little while. I did restart the PC after uninstalling just in case. Then after reinstall Creative Cloud Desktop app, the problem solved! App list and tabs, other contents are shown in the window normally! (It didn’t require a login or other operations)
↓ A tweet became clue for the solution. ↓
— アドビ サポート担当 (@AdobeSupportJ) March 13, 2019
I’ve been encountering this problem time to time… Why a user who is paying 6,248 yen per month (including tax), rather, 65,836 yen per year (including tax) has to troubleshoot by himself each time when the problem occurred!? C’mon Adobe! Seriously.🤬
By the way, I found a tweet that reinstalling doesn’t fix the problem. Adobe should reflect on that.
— eight@プログラミング勉強中 (@luna_Key) March 26, 2018