Windows boot sequence spends a long time on Adobe NotifyChangeDirectory operations

[adamfp]

I'm trying to figure out why my Windows 11 bootup time was longer after I upgraded my PC.

Running procmon showed me that 19 out of the 23 longest events were Adobe 'NotifyChangeDirectory' operations, mostly for 'node.exe'

Any advice on how to speed this up or stop it from happening? Can I delay these operations until after Windows has loaded? I don't really know what I'm doing so any advice would be appreciated.

[kglad]

did you update an older os to win 11?

do/did you have older adobe apps on your win 11 computer?  

if not, did you migrate anything to your win 11 computer?

[adamfp]

Thanks for responding.

I updated windows 10 to 11, upgraded RAM, CPU, mobo and a clean Windows/Creative Cloud install on a new boot disk.

But I potentially left some older Adobe apps or support files are still on a different disk and I might have migrated a couple of AE + PR settings files.

[kglad]

you should clean your computer of adobe files and reinstall:

uninstall every cc app including preferences per https://helpx.adobe.com/creative-cloud/help/uninstall-remove-app.html

then uninstall the cc desktop app, again using the correct uninstaller per https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html#sa_src=web-mes...

clean your computer of cc files per http://www.adobe.com/support/contact/cscleanertool.html

restart your computer (don't skip this)

reinstall the cc desktop app using the "alternative download links" at the bottom of the page at https://helpx.adobe.com/download-install/kb/creative-cloud-desktop-app-download.html

use the desktop app to install your cc programs/trials

NOTE: win 11 users that have trouble with the latest win 10 installer often have success with the older win 10 installer.

[Abambo]

Look at the longest events first. Looks like they are all Microsoft.

You can really only do correct assumptions by comparing the old boot sequence against the new boot sequence when you have data to compare.

[adamfp]

Thanks for responding.  I figure that Win32 isn't going anywhere but having Adobe run time-consuming operations during boot might not be strictly necessary.

Some of the other logs I've taken aren't as Adobe-heavy but it always figures somewhere in the slow operations list.

[adamfp]

*I meant system32 not Win32