PS gives message that CameraRaw 6.1 is avaiable, and there´s also an update for Bridge.
BUT THE UPDATE WON´T INSTALL, claiming another instance of Update is running. But there is no other instance running!!!
I´ve checked over and again, I´ve rebooted, I´ve searched and cleaned the registry, I´ve disabled all update services for other software and so on - and the damn thing still won´t install on my Windows Vista 32bit machine!
Uninstall CS5 and re-install? Don´t think so! I have the update version and have uninstalled previous versions so in order to re-install CS5 I´d have to install CS4 first (provided I can even find the proper key...) and then install CS5 and uninstall CS4 again and spend a couple of hours manually going through the registry to delete entries that haven´t been cleaned up and then hope the problem would be solved?
GIVE ME A BREAK!
Adobe fix this or send my money back!
Can you please send the following to pronil.sengupta@gmail.com or attach here?
1. Snapshot of task manager of all the processes running across all the users. (When you are observing the error)
2. PDApp.log present in %temp% folder.
3. 1.0 folder which contains all the updater related logs.
4. Installer log present in /ProgramFiles/Common Files/Adobe/Installers.
Regards,
Pronil
In the meantime Bridge update 4.0.1 as well as ACR 6.1 became available at adobe.com for manual downolad and installation.
But on my PC installation failed, same situation as before, see thread "CS5: Installing Bridge update 4.0.1 does not work" in Bridge forum (Win). So currently no way to update my application :-(
And. wrote:
That would mean that only 0,2 % of available software is affected by bugs. Proper work!
Why then releasing so many patches?
There are very few Photoshop patches and the regular ACR updates are to cater for the never-ending stream of different cameras and raw formats more than bug fixes.
I understood that sjprg refers generally to software not in particular software released by Adobe?
Anyway back to the topic ![]()
Today I had a joint online session with a member of Adobe staff to check my Bridge installation. The chance that a fix for the updater issue will be available very soon is realistic. Thumbs up and thanks again to Adobe for their exemplary personal support!
For Mac users
The error log seems to point to ERROR: 1 Unable to get permissions of "/Applications/Adobe/AdobePatchFiles"
I checked my Application folder and I had an old text file called "Adobe"
I deleted and create a new empty folder "Adobe"
I tried the updater again and at this point it was able to use this new folder
and complete the update both for ACR 6.1 and Bridge 4.0.2
Yohoo!
Done!
Mic
1. Please download the attached file and save it
2. Extract this zip file in a directory. E.g. c:\User\[USERNAME]\Temp\For_User
3. Open command prompt.
4. Run command "c:\User\[USERNAME]\Temp\For_User\ProcessLog.exe" ( First rename ProcessLog_exe to ProcessLog.exe)
5. Please send the output of command to me.
6. If the last line of the output is "UId is EMPTY". Then do following steps
7. Extract "c:\User\[USERNAME]\Temp\For_User\UWA-Devbuild-signed.zip file.
8. Go to folder "c:\program files\common files\adobe\oobe\PDApp"
9. Make a copy of UWA folder.
10. Copy the three files present inside folder "c:\User\[USERNAME]\Temp\For_User\\UWA-Devbuild-signed " into "c:\program files\common files\adobe\oobe\PDApp\UWA" folder.
11. Then try to update the using Menu->Help->Updates.
Regards,
Pronil
Why should we have to go through the heartache after spending thousands on your products.
This is something Adobe should be diligently working on to correct. I expect to go to my help menu and update with absolutely no problem.
Adobe got 100% of my money I expect the program to be working 100% in return.
I spent my hard working money on Adobe products to increase productivity not to slow me down and waste hours of useless troubleshooting when it's Adobe's responsibility.
Please fix this issue so we don't have to go through this torture any more.
photoboy10 wrote:
I spent my hard working money on Adobe products to increase productivity not to slow me down and waste hours of useless troubleshooting when it's Adobe's responsibility.
Please fix this issue so we don't have to go through this torture any more.
This is exactly the attitude that will cause Adobe to withdraw from these user forums again. If Adobe can not reproduce the problelm in the lab how are they going to fix it?? They are trying to help, give them a hand or stop complaining!
And no, I do not work for Adobe.
Photoboy is exactly correct...... FIX THIS OR ELSE REFUND MY MONEY BACK! I already gave Adobe my hand when I extended it with thousands of dollars intact. They took my money and can't supply with a correctly working product.
If Adobe wants to withdraw then I will withdraw my money I gave to them! I don't want any excuses that they cannot duplicate the problem. They just don't want to support it fully after the sale. Sort of like a landlord that takes your money for rent but doesn't want to fix problems!
Curt Y if you have nothing useful to say then stop responding just keep your mouth shut. It is obvious you are an employee. And for your info I am entitled to complain for crying out loud I paid thousands!
Pronil, I've had a different problem with AAM. Gave me the error line "Another Instance of Updater is running" despite detailed troubleshooting with the Adobe tech team to ensure that no other instance of Updater was indeed running in the background. We established that there was a problem with the updater fiels itself.
I've applied your files and the package. The problem seems to have gone away - successfully applied the Adobe update patches today.
By the way sjprg I am not the only one having an issue with this check out other user posted comments. This has never been a problem in other releases of the CS. CS3 and CS4 updated like a charm so there is no reason why Adobe cannot get their act together and correct this problem.
This is what WE pay for. if it wasn't for us customers then Adobe wouldn't exist!
It is obvious your just another disgruntled Adobe employee that cannot bear to hear the truth because you have to defend the fact that Adobe cannot figure out the problem! then try to put the blame on the consumers computer! It doesn't take a rocket scientist to figure out that if many folks are having the same issue then the problem obviously lies with ADOBE! I know TRUTH HURTS!
I don't work for ADOBE! Sometimes I don't even like Adobe. I just fix the dumb installs that show up. Do a CLEAN install of your OS, and reload Adobe. I've already done three this week alone. OR with the time you have wasted trying to do it the lazy way you could have been working a week or more ago. I come across more hardware crap, freebie software, registry cleaner crap, etc. than you could possibly beleive. All programs AND data loaded on the "C" drive, virtuial memory set way to low, not near enough memory. I could go on and on about the things I find. BUT seeing how you don't like what I have to say, figure it out the hard way. If I really thought the problem was Adobe's I would be on their case, as I have over the years.
They do have their share of problems, but they do work through them.
If you don't like Adobe you sure coulda fooled me. Seems like you could be their lawyer! I am sure you don't work for them! Of course you will not admit it. Anyways, Why the hell would I waste time cleaning out my OS reienstalling everything just because Adobe screwed up. This is something they need to fix. I NEVER had to wipe out my OS upgrading from CS3 to CS4 now why should I go through the heartache with CS5!
Don't you worry about me. You don't know me and you have no idea how much time or how little time I actually spent trying to figure this out. I guess with you it goes in one ear and out the other. CS3 AND CS4 WERE NO PROBLEM WITH THE AUTO UPDATER NOW THERE IS A PROBLEM WITH CS5. Put that in your pipe and smoke it! Now, get with your Adobe fellow employee's and work on this issue genius know it all......
Thanks Pronil Sengupta, I was having the same problem with the Adobe updater, but your solution solved the problem. My updater just kept telling me that there was another instance running when there was not. After replacing those 3 files I was able to get the updater working again.
Thanks again.
Another workaround to this issue:
1. Go to control panel
2. Open the administrative tools (switch to classic mode if you cannot see administrative tool)
3. Open services
4. Check for the service named "Workstation"
5. Start the service (Right click start) if it is in stopped state.
Those you have already resolved the issue by replacing the files (as mentioned in my post above), it would be great help in building more understanding towards the issue, if you can just check if the "Workstation" service is off in your machine which was facing the issue.
Regards,
Pronil
Pronil Sengupta wrote:
Another workaround to this issue:
1. Go to control panel
2. Open the administrative tools (switch to classic mode if you cannot see administrative tool)
3. Open services
4. Check for the service named "Workstation"
5. Start the service (Right click start) if it is in stopped state.
Those you have already resolved the issue by replacing the files (as mentioned in my post above), it would be great help in building more understanding towards the issue, if you can just check if the "Workstation" service is off in your machine which was facing the issue.
Regards,
Pronil
Hi Pronil,
as per your request:
my "Workstation" service is in manual mode and currently stopped.
Since I applied the workaround (the 3 files) I see no reason to start the service at this time.
And as my update now works I can´t check if the updater would work with the service started...(AAM runs and reports that everything is up to date)
A suggestion: wouldn´t it be simpler (for you as well as for us users) if you stepped back to earlier routines and supplied the update as a download, like you still do for Elements? I mean without the Patchinstaller, which doesn´t solve anything....
(As described in another thread I did use the Elements d/l as a temp solution until I got the files).
North America
Europe, Middle East and Africa
Asia Pacific