Adobe Application Manager Errors

Report · Feb 18, 2018

For the last week or so I'm seeing an error message in my Windows 10 Application log on every boot, and then repeated at random intervals.

The error is this -

Faulting application name: AAM Updates Notifier.exe, version: 9.0.0.281, time stamp: 0x5776ade0

Faulting module name: UpdaterCore.dll, version: 9.0.0.30, time stamp: 0x5773799f

Exception code: 0xc0000005

Fault offset: 0x0006287e

Faulting process ID: 0x2a30

Faulting application start time: 0x01d3a8c7ece02e87

Faulting application path: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\UWA\AAM Updates Notifier.exe

Faulting module path: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\UWA\UpdaterCore.dll

Report ID: 6e36136e-8581-4762-aa2c-41421964a69a

Faulting package full name:

Faulting package-relative application ID:

I have tried to uninstall and reinstall AAM, but there seems to be no uninstall option for it.

I downloaded the latest version and just reinstalled it, which seemed to work OK, but the error messages are still there.

I'm not 100% sure, but they may have started when Windows 10 was last updated on "Patch Tuesday" last week.

Is this a known issue?

Things do seem to be still working OK apart from the error messages.

AAM Updates Notifier.exe is not shown as running in my Windows Task Manager. Should it be?

This is the standalone version of AAM, not the version included with the Creative Cloud App, which I don't use as it constantly nags me to update an application I haven't got installed. This is due to a bug triggered by the presence of Premiere Pro CS6 on the system, which has never been resolved.

I only have one actual CC application installed (Muse) so I've never seen any need to have the CC App installed anyway.

Any help gratefully received!

Cheers,

Dave.

Report · Feb 18, 2018

Follow below steps :

If installed, Uninstall Adobe Creative Cloud .

Creative Cloud Help | Uninstall the Creative Cloud desktop app

Disable Firewall Temporarily.

Step 1 :

Open C:drive and navigate to C:\Program Files (x86)\ " Common Files" \Adobe.

Open Adobe folder and delete folders named Adobe Application Manager and OOBE.

Step 2:

Navigate to C:\Program Files (x86)\Adobe.

Open Adobe folder and if present delete Adobe Creative Cloud folder. [**important]

Unable to delete??? rename it to Adobe Creative Cloud-old.

Step 3 :

Press Windows button (located between Ctrl and Alt buttons) along with R button together at a time , you will get a run command window.

Type in below command and hit 'Enter' key.

appdata

Then navigate to Local>Adobe.

Open Adobe folder and delete folders named AAMUpdater and OOBE.

Step 4 :

Make sure Adobe Creative Cloud is not listed under Control Panel > Program and Features. list.

Click on the below link and download Adobe Application manager and install the same :

http://download.adobe.com/pub/adobe/creativesuite/cc/win/ApplicationManager10.0_all.exe

Once the installation process is completed, locate Adobe Application Manager launch icon on Desktop and double click on it .

It will start update process.

once it is completed,

it shud launch Adobe Creative Cloud app.

Report · Feb 19, 2018

Thanks!

I've been through the steps detailed.

As I said, I don't have the Creative Cloud Desktop App installed, and haven't had for a very long time.

In step 1, there was no Adobe Application Manager folder present, but I deleted the OOBE folder.

In step 2, there was no Adobe Creative Cloud folder, as expected because the Desktop App isn't installed.

Everything else seemed to be fine, and I reinstalled the standalone Adobe Update Manager apparently successfully.

There are no more error messages, which is good!

However, I now have another issue, I cannot use Muse any more!

When I run it, it asks me to sign it, as expected, but when I try to sign in I get an error message saying -

"Please connect to the Internet and retry. Either your computer is offline or the clock on your computer is set incorrectly, causing a connection error."

Needless to say, my computer clock is correct, and I am online, or I wouldn't be able to submit this!

Any ideas? I now can't use anything!

Dave.

Report · Feb 19, 2018

Update!

I just looked in my error log, and one AAM Updates Notifier.exe error had appeared again.

I then tried running Muse again, and this time it did log in successfully, so at least I can now use it again!

I rebooted and the log error did not immediately reappear, so I'll keep and eye on it and see what now happens.

incidentally, when I click on "Updates..." in the help menu of Muse, nothing apparently happens.

Is that what would be expected if there were no updates available?

I would expect to get some sort of message at least.

Cheers, Dave.

Report · Feb 20, 2018

Still no joy I'm afraid, the error message is back again today as before.

Once just after boot, and then again a few minutes later.

Faulting application name: AAM Updates Notifier.exe, version: 9.0.0.281, time stamp: 0x5776ade0

Faulting module name: UpdaterCore.dll, version: 9.0.0.30, time stamp: 0x5773799f

Exception code: 0xc0000005

Fault offset: 0x0006287e

Faulting process ID: 0x2448

Faulting application start time: 0x01d3aa688dd606b4

Faulting application path: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\UWA\AAM Updates Notifier.exe

Faulting module path: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\UWA\UpdaterCore.dll

Report ID: 290e8541-b811-4224-bee9-e348a1bf6d6f

Faulting package full name:

Faulting package-relative application ID:

Any other ideas anyone?

Cheers,

Dave.

Report · Feb 26, 2018

Anyone any ideas what could be causing this?

If I manually run AAM Updates Notifier.exe it runs briefly, and then closes, generating the error message.

Running it as an administrator makes no difference.

I think this is some sort of bug which has started with the latest updates to Windows 10.

How can I report this to Adobe for investigation?

Thanks, Dave.

Report · Feb 28, 2018

I am experiencing the same issue and have tried the suggestions but they have not been successful. I have not done a complete uninstall and reinstall of Lightroom and Photoshop because of the customizations and because there is no assurance that all that work would actually solve the problem. What I have done to stop the AdobeUpdateService and set it to disabled as a temporary fix. Not positive that this will work but until a better solution is available its worth a try. I'll report back in in 24 hours.

Report · Feb 28, 2018

Well I'm glad it's not just me!

If you look back in your Windows Application log, did your error messages start around the same time as the last set of Windows 10 updates, on February 13th?

Report · Feb 28, 2018

Hi DaveH5. Yes they did so I suspect that we are looking at a WIn10 issue. But the only thing that installed on 2/13 was a minor update of a Windows Store app, 9WZDNCRFJ3PM-Microsoft.WindowsPhone. There was a buggy update (KB 4074588) that installed on 2/14 that's caused lots of issues for other users but the dates just don't align for us. I'm a member of the Windows Ten forum so I'm going to post a message there in a few minutes. We have lots of very savvy users there so maybe we can get some feedback.

Is there a way to get Adobe attentions on this issue? FYI, I'm new to this forum.

FIRST UPDATE: I searched the Windows Ten Forum and found a similar issue. Unfortunately it appeared to never have been resolved. I've run diagnostic software that was requested in that previous thread and uploaded it to the Forum along with new details of the issue so hopefully we'll l find some who is experienced in reading the results and who is willing to help. I'll update on progress,

SECOND UPDATE: Decided to take matters into my own hands and prevent this annoying issue once and for all. I went to Services and stopped the Adobe Update Service and then set it to Disabled. Next I went to Task Scheduler and found Adobe AAM Update set it to disabled by highlighting the task, selectin properties in the right hand window, selecting edit and then unchecking the Enable check box. That should take care of the annoying errors.

Interesting enough the Adobe AAM Updater task was shown as having successfully run on its last operation. This is probably due to the problem, lying in the programs DLL and not the EXE.

It also appears that the Adobe Creative Cloud app still works fine when you manually check for app updates. So unless and until someone comes up with a better fix I'm going with this interim solution.

Report · Feb 28, 2018

Thanks, that's really helpful.

I don't have the Creative Cloud Desktop App installed, as it causes other problems for me, so I rely on the Application Manager to tell me if there are any updates available for Adobe Muse, which is my only installed Creative Cloud application.

I hope this is fixed soon. I've had other applications break in the past when Windows 10 has been updated, and they have always been OK after an update, so I hope that's the case this time too!

Cheers, Dave.

Report · Mar 01, 2018

Hi Dave, If you decide to kill AAM them you could use the Update selection on the Muse Help menu to periodically check for updates manually. Is Muse updated all that frequently, I've never used it?

I am wondering why this issue started before the last major Win10 update. That make me wonder if its something else going on like maybe our AV. I use Norton Security along with Malwarebytes. What do you use?

I checked the Norton Security logs and there were no events listed around the time of my last AAM failure so that's looks like another dead end. I'd love to hear from someone else who has had this issue and who has done a remove and reinstall.to see if that really does solve the issue. If it doesn't then that would be strong evidence that its a Win10 issue.

Thinking maybe I could run a fill image backup of my system and then do a uninstall/reinstall of Lightroom and Photoshop just to see if it works. I always hate to fool around with my main PC with stuff like this but I'm really curious.

Bob R.

Report · Mar 01, 2018

Thanks Bob, sorry for the delay in responding.

I didn't realise that the "Update" option on the Help menu of Muse didn't depend on all the Application Manager programs running.

I assumed that the "AAM Updates Notifier" program was part of that, and update checking and installing wouldn't work without it.

Whenever I try that menu option it doesn't seem to do anything, even before the present issue, which may just be because there were no updates actually available of course, but the fact that it has three full stops after the menu entry normally means that it should open another window, which never happens.

I've checked my AV. I only use the built-in Windows Defender on Windows 10, and disabling it does not allow AAM Updates Notifier.exe to stay running.

Cheers, Dave.

Report · Mar 02, 2018

Hi Dave. NP, I understand being busy.

I think AAM Updates Notifier runs once a day in the background to determine if an update is available. The Application Manager that can work in conjunction with the Creative Cloud App or work without it, in your case, actually retrieves the update when the user asks for it.

The Notifier is what's hosed on our PCs. But it sounds like the Creative Cloud App was giving your PC issues as well so you've uninstalled it, right?

Yesterday I removed the Notifier (again) and installed the newer version and re-enabled it in Task Scheduler. Sadly, the Notifier error reappeared this morning. So what I've decided to do is to uninstall Lightroom, Photoshop, and the Creative Cloud App and reinstall them. If the error persists then we'll know its Winows10 and not Adobe. Good thing I'm retired and have the time tp play with this.

I'll let you know if the Notifier error comes back tomorrow at login.

Bob R.

Report · Mar 02, 2018

Thanks again Bob.

My understanding now from what you're saying is that if the AAM Updates Notifier program is not running because it's crashing, I won't receive any automatic notification of any updates, but a manual check for updates should still work.

That's good to know anyway!

The reason I uninstalled the Creative Cloud Desktop app is a very long story.

It worked fine for ages, but then one day after an update it started nagging me on every boot to install an update to Adobe Acrobat DC, an application I didn't even have installed on my system!

Acrobat DC even spuriously appeared in my list of installed applications!

To cut a very long story short, despite numerous support sessions with remote control of my computer by people from Adobe technical support, this was never resolved. I was even told at one point that this was expected behaviour and I should just put up with it or turn the notifications off! This was obviously nonsense, and I would lose the notifications that I did want to see if I just switched them off, so I didn't give up pestering Adobe support to find an answer.

Eventually it turned out that what was triggering the problem was that as well as Muse, I also have Adobe Premiere Pro CS6 installed, which is not a Creative Cloud application of course. If I removed it, the nags about Acrobat DC went away.

They still never managed to explain what the root cause was though, so as it turned out that I didn't actually need the Creative Cloud Desktop app for Muse to work, and the standalone AAM does the job just as well, I just uninstalled the Creative Cloud Desktop app, and have no intention of putting it back again if I can help it!

Good luck with your investigations!

Cheers, Dave.

Report · Mar 02, 2018

Hi Dave, Sad commentary on tech support. Even sadder is that this is becoming more the norm.

I just uninstalled Lightroom, Photoshop, and Creative Cloud with no problem but when I uninstalled AIR the uninstaller hung and I had to use Task Manager to kill it. Not good. So I decided to make sure that windows system files were OK before I did anything else. More and more people, including me, are discovering that after windows updates, system files often need to be repaired using SFC and also DISM if necessary. You might want to try this. Its non-destructive and very safe to do and often solves a ton of windows issues. If you haven't done it before here's a quick tutorial.

1. Enter CMD in Cortana.

2. When the Command Prompt desktop app appears, right-click on it and pick "Run as Administrator" and let the app make changes to your system.

3. When the CMD window appears enter this:

sfc /scannow (space before the "/")

4. Let it run, it takes a while. This repairs the system files.

5. When it completes and if it says it found no errors, great.

6. If it found errors and repaired them then restart your PC and run it again, restarting each time, until it finds no errors. You might need to do it up to 3 times.

7. If SFC finds errors but cannot repair them then in the same window enter:

dism /Online /Cleanup-Image /RestoreHealth (space before each "/") This repairs the repository that SFC uses to fix files.

8. After its done then run SFC /scannow again and you should be good.

Again this will not damage your PC and it might fix the Update errors. If you have questions let me know.

You might want to do this each time an significant update occurs or if you see anything wonky happening.

On a positive note my reinstall of Lightroom Classic CC, Photoshop CC 2018, went flawlessly. All customization were found and even mu customized Lumenzia workspace was intact - so great!

Now we'll see if tomorrows startup is error free.

Cheers, Bob R.

Report · Mar 02, 2018

Yes, I've run both those commands quite a few times over the years to try and correct errors.

Sometimes they fix them, sometimes they don't!

It's been quite a while since I last did it though, so I gave it a go.

sfc /scannow said it found errors and corrected them, so I rebooted and ran it again, and the next time it was clean.

No errors seen since on a couple of reboots, but early days to be sure. I'll keep you posted!

Good thought!

Report · Mar 03, 2018

Hi Dave,

I'm sad to report that repairing the Windows10 system files and removing and reinstalling Lightroom, Photoshop, and Creative Cloud Desktop App did not resolve the AMM Updates Notifier errors. Since Adobe did not appear to update any of its apps on or before the onset of the issues on my PC (2/13), I think this might be caused by the 9WZDNCRFJBH4-Microsoft.Windows.Photos app that was updated on 2/10 on my PC, the last time I ran my PC prior to the errors. Unfortunately there's no way for me to test that theory because removing an app like that results in its immediate reinstallation on the next boot.

Until Adobe and MS can resolve this all I can do is disable the AdobeAAMUpdater-1.0 in Task Scheduler and periodically check for updates through the Creative Cloud apps.

Hope this annoyance gets resolved soon. All the best,

Bob R.

Report · Mar 03, 2018

Yes, I'm afraid that the error is still there for me too Bob.

Report · Mar 04, 2018

I too am having problems with the AAM crashing on a daily basis, and I disabled it in Services and in the Task Scheduler. All was OK for a couple of days and then I installed Bridge from the Creative Cloud app and the errors began again. I note that people are putting the event down to a possible Win10 error that appeared after the 13-2-18 update for Windows photos. I did some digging and I found out how to remove Win 10 apps. It is done via the Power Shell app. here is an article about it:

How to Uninstall Windows 10’s Built-in Apps (and How to Reinstall Them)

I use photographic tools on Windows, so I am a bit loathe to do it, but it a simple process - I uninstalled Windows Phone as I don't have any need of the app, but it might be worth a try?

Regards

BobD

Report · Mar 04, 2018

Thanks BobD.
I had a brief online chat with Adobe support yesterday, but apparently the team that deals with this area doesn't work at weekends, so I'm going to try again tomorrow!

It would be very strange IMO if an update to one Windows 10 app would have caused the problem, I was assuming that the last "Patch Tuesday" update to the Windows system files would have been much more likely to have triggered it.

I'll wait and see what the support guys say tomorrow.

This is not unknown in my experience, I have had other background programs start to malfunction and crash after Windows 10 updates, and the problem has had to be addressed with an update to the programs concerned. I suspect that will be the case this time too.

Report · Mar 04, 2018

Hi Dave. I'm looking forward to your call to Adobe support. I have some info that might help.

Yesterday I installed LR, PS, and the Creative Suite Manager on a another PC that is very similar to the one I'm having the issues with (both are Dell XPS 8700). Both are Win10, same version/build and both are up to date. FYI, the second one is used just for gaming. This morning there was no AAM Updates Notifier error on the 2nd PC. This points to Win10 app patches and the last major updates not being the cause.

Further the last 2 MS updates (KB890803 Malicious Software Removal Tool and, KB4074588 2018-02 Cumulative Update) did not install on my PC until (2/14) the day after the AAM Updates Notifier errors began (2/13). I got the updates one day after Patch Tuesday because I had my PC on early on 2/13 and for just an hour so which was before the MS servers released the patches to my area. I do know that KB4074588 was buggy and caused problems. MS quickly pulled it and released a new version later in the day so I probably got the corrected version. This makes me think that MS Updates are not the issue, if so it would be much more wide spread and my second PC was show the same issue.

FYI, I've had no responses to my request for help on the Win10 Forum and no response to the message that I sent to a forum member who had the same issue back in 10/17.

Until I read your post this morning I was thinking of doing an in place upgrade of Win10 but now not so much. I'm thinking its another piece of software that's installed a DLL or modified a registry setting. I've been wondering if maybe Acrobat Standard V9.5.5 that I have installed might be the problem. For several years I had the the Adobe Acrobat Update in Task Scheduler disabled to avoid problems with the new Reader DL installing. Maybe that has something to do with it, although its probably a long shot?

FYI, I discovered that Adobe has a great tool called LogCollectorTool.exe that gathers info on issues. You can run it and email the zip file to Adobe support. I looked through mine yesterday and can definitely see the errors with the AAM Notifier but I'm not skillful enough to trace the contributing events by the Adobe software engineers would be. You can get the tool here if you interested:

Log Collector Tool

Here's the text of the link in case the forum strips the link out:

“https://helpx.adobe.com/creative-cloud/kb/cc-log-collector.html”

I'd be willing to send my results to Adobe if they are interested.

Let me know what happens tomorrow.

Bob R.

Report · Mar 04, 2018

Hi krfpv evff. Sorry I overlooked your post earlier this AM when I replied to DaveH5.

I just checked on my second Win10 PC that does not display the AAM Notifier errors and the photo app is installed on it. Have you gone through a cold start in the morning after removing the photo app without an error?

So it looks like the cause of the AAM Notifer error is something that is common to your PC, DaveH5's, and one of my PCs but NOT my second PC. Too bad we can't put them side by side to compare them! It might be something that has to do with the sequence in which DLL files get updated. I'm thinking that this is going to take an Adobe software engineer look at the our error logs to figure out.

It least its not something that preventing us from using our PC.

Bob R.

Report · Mar 04, 2018

I just tried as an experiment uninstalling KB4074588, which was the last main update to Windows 10.

Sad to report, this did not result in the error messages stopping, so I let it install again.

There was one other update at the same time, KB4087256, which was for the Windows 10 Servicing Stack.

Unfortunately this update is not removable, at least not by normal means, so I was unable to test whether it's relevant to the problem or not.

Report · Mar 04, 2018

Hi David. Sorry that didn't help.

I found this at windows - What is the servicing stack and how does it work? - Super User

"the servicing stack which seems to fulfill the role of a package manager. I don't understand it very well, only that it seems that Component-Based Servicing (CBS), Windows Installer, Windows Update, and WinSxS are part of the servicing stack or are otherwise involved in servicing."

"Servicing is the act of installing a role, feature, service pack or windows update against a Windows OS. Most of the time servicing is done in an online state. In this case, online means that the operating system is up and running when a change is made. Online servicing is what most people do and is usually done via Windows Update or double clicking a downloaded update. There is also an offline state. Offline, of course, means that the installation is happening against a non-running version of Windows. This is what a lot of larger corporations and OEMs do with their image files, they mount them with IMAGEX or DISM and then install hotfixes or other updates against those images to reduce their patch time when the image is rolled into production."

It doesn't sound like that the culprit and again it was installed on my PC a day after the errors began.

I sure hope Adobe Help is interested enough to bump this up the line to a software engineer.

Cheers,

Bob R.

Report · Mar 06, 2018

Hi again guys!

I had my chat with Adobe support yesterday, and was passed to the Muse support team.

The guy tried to persuade me that I needed to have the Creative Cloud Desktop app installed, and said that CC applications don't work with the standalone Adobe Application Manager, which isn't true!

When I made it clear that I wasn't going to have him put that back, because of previous problems, he went away to consult, and then came back and renamed a folder to disable it.

The folder appeared to be empty apart from a "1.0" subfolder which also appeared to be empty, so I really didn't think this would do any good, but lo and behold, the errors then went away, and I haven't seen one since!

The folder concerned is C:\ProgramData\Adobe\AAMUpdater.

The guy renamed it to AAMUpdater_old.

When the Updater scheduled task was run again, the folder was re-created, but no error message!

The new folder is still empty, apart again from a subfolder called "1.0", which is also empty.

I asked the guy how on earth just effectively deleting and recreating an empty folder could have cured the fault, and he said there were actually hidden files in it.

This is quite bizarre to me, as when I checked more thoroughly after the chat session was over, both the original folder and the new folder definitely have no files in them, or their "1.0" subfolders, not even "super hidden" ones!

So, give this a try and see if it fixes it for you as well!

If it does, I have absolutely no clue as to why it has!

Cheers, Dave.

Adobe Application Manager Errors

1 Correct answer