v1.9.652 won't install updates

[jeffweiss9]

Hi,
 I deleted my old version 1.6.9(?) and installed 1.6.9.651as I understood that was a completely new release.  That installation proceeded without incident, although I didn't test the operation of the program much since it immediately asked to install two updates (I think to make 1.6.9.652) but those undates will not install on my Dell Latitude E6400 laptop (XP SP3 32-bit).  When I leave PI and it asks to do the installation, I get a window appearing asking me which user:
1) my normal login account on the computer (jweiss) which does NOT have administrator privilege from which I run ALL programs.
2) the administrator account.
If I choose 1), I get a message that the installation has failed and the update log file is blank.
If I choose 2), I get the following message:

Unable to open file: C:/Documents and Settings/jweiss/Local Settings/Temp/PixInsight 32-update/contents/updater1.log: Win32 error (32): The process cannot access the file because it is being used by another process.

Either way, the updating process fails on my machine.  Is there a fix or work around for this?  (I do not want to have to login to the administrator account ONLY to run PixInsight).

I don't know if it's related to not getting the updates, but ALL processes now say 'no available documentation', instead of the 4 or 5 that has documentation previously.

Thank you.
-Jeff

PS I had no problem installing and updating on my main computer which is an HP Elite HPL-450t Win7 64-bit machine.

[Juan Conejero]

(I do not want to have to login to the administrator account ONLY to run PixInsight).

And you don't have to do that.

When XP asks you what user should run the installation, you can:

- The easiest way to proceed is unchecking the "Protect my computer..." option and run the installation as yourself (the current user). Note that if you don't uncheck the option the installation will fail.

- If you have an Administrator account with a password (or other account with administrative privileges), then you can enter the corresponding password and run the installation as that user. Note that in this case a password is mandatory; without it the process will always fail.

We have tested the update installation process in both ways and it works without problems on Windows XP 32-bit.

As you have already seen, Windows Vista and Windows 7 support UAC (User Account Control), which makes software updates much easier and secure. Unfortunately, Windows XP does not support UAC and makes everything more cumbersome.

Let me know if this helps.

[jeffweiss9]

Thanks very much, Juan-
  Of your two methods, the second one is my 2) above that I tried with the resulting error message.   However, before going back to try your first method, I checked that, in fact, I now have version 1.6.9.652 rather than 651.  So, in spite of the error message, it appears to have successfully installed the 652 updates and I do now see the documentation files again.
Clear skies,
-Jeff

[slang]

(I do not want to have to login to the administrator account ONLY to run PixInsight).

And you don't have to do that.

When XP asks you what user should run the installation, you can:

- The easiest way to proceed is unchecking the "Protect my computer..." option and run the installation as yourself (the current user). Note that if you don't uncheck the option the installation will fail.

- If you have an Administrator account with a password (or other account with administrative privileges), then you can enter the corresponding password and run the installation as that user. Note that in this case a password is mandatory; without it the process will always fail.

We have tested the update installation process in both ways and it works without problems on Windows XP 32-bit.

As you have already seen, Windows Vista and Windows 7 support UAC (User Account Control), which makes software updates much easier and secure. Unfortunately, Windows XP does not support UAC and makes everything more cumbersome.

Let me know if this helps.

Hi Juan.

I have exactly the same problem as JeffWeiss9 - whenever 1.6.9.651 attempts to update, I get the same error message - "Unable to open file: C:/Documents and Settings/steve/Local Settings/Temp/PixInsight 32-update/contents/updater1.log: Win32 error (32): The process cannot access the file because it is being used by another process."

I'm using XP Pro (32 bit), latest Service Pack. I run as a local unprivileged user (steve), and when it attempts the upgrade, it asks for local admin details, which I give it. I don't have a problem with other local admin commands - I regularly have a cmd shell as local admin as well as several as unpriv'd as well.

I have checked, and there doesn't appear to be another process that has that file open that I can tell. I have tried rebooting to get a 'clean run', but that didn't help. Unlike JeffWeiss9, mine is stuck on 651 for now... Previous updates have worked OK for me.

This update came out some time ago, and I've been holding off restarting and updating, as I was in the middle of a long workflow - maybe a week or more. I've had several hibernations in this state, but never a problem like this before.

Is there _anything_ that I can do to clear this error out, and get updating working again?

Cheers -

[slang]

(I do not want to have to login to the administrator account ONLY to run PixInsight).

And you don't have to do that.

When XP asks you what user should run the installation, you can:

- The easiest way to proceed is unchecking the "Protect my computer..." option and run the installation as yourself (the current user). Note that if you don't uncheck the option the installation will fail.

- If you have an Administrator account with a password (or other account with administrative privileges), then you can enter the corresponding password and run the installation as that user. Note that in this case a password is mandatory; without it the process will always fail.

We have tested the update installation process in both ways and it works without problems on Windows XP 32-bit.

As you have already seen, Windows Vista and Windows 7 support UAC (User Account Control), which makes software updates much easier and secure. Unfortunately, Windows XP does not support UAC and makes everything more cumbersome.

Let me know if this helps.

Hi Juan.

I have exactly the same problem as JeffWeiss9 - whenever 1.6.9.651 attempts to update, I get the same error message - "Unable to open file: C:/Documents and Settings/steve/Local Settings/Temp/PixInsight 32-update/contents/updater1.log: Win32 error (32): The process cannot access the file because it is being used by another process."

I'm using XP Pro (32 bit), latest Service Pack. I run as a local unprivileged user (steve), and when it attempts the upgrade, it asks for local admin details, which I give it. I don't have a problem with other local admin commands - I regularly have a cmd shell as local admin as well as several as unpriv'd as well.

I have checked, and there doesn't appear to be another process that has that file open that I can tell. I have tried rebooting to get a 'clean run', but that didn't help. Unlike JeffWeiss9, mine is stuck on 651 for now... Previous updates have worked OK for me.

This update came out some time ago, and I've been holding off restarting and updating, as I was in the middle of a long workflow - maybe a week or more. I've had several hibernations in this state, but never a problem like this before.

Is there _anything_ that I can do to clear this error out, and get updating working again?

Cheers -

I finally managed to fix this - been bugging me for a long time now. I ran PI under the local administrator user. Then did the update, and restarted - all was fine. Then, when starting under a non-privileged user, it's also running the updated version.

What I think was happening....
I use makemeadmin.cmd (Aarom Margosis) so that I can run as a non-privileged user, and run some progs as admin if required. REF: http://blogs.msdn.com/b/aaron_margosis/archive/2004/07/24/193721.aspx
A recommendation in that article is to change the Windows behavior so that if you are running with temporarily elevated privs, what create will be owned by admin group, and not the local user. My suspicion is that this is affecting/conflicting with the upgrade process when the PI is started as an unpriv'd user, and they follow the process and authenticate as admin during the ugprade process.

Either way, my prob is resolved, so I'm pretty happy about that... until the next upgrade that is....