I
Ian
I have Office XP standard installed, displaying 'SP-1' in
Help/About from each product. The product is activated,
but forms part of a Volume Licence arrangement from the
retailer I used (Ramesys in UK).
On attempting Office update from
http://office.microsoft.com/officeupdate/default.aspx,
the 'Check for updates' suggests that I need SP-1 and a
security update for MS Project (KB822211), 6Mb total. All
other updates are greyed out (dependent on SP-1). On
starting the installation, after EULA, confirmation
and 'have your product CD ready' screens, the download
screen appears but then closes very quickly
with 'installation unsuccessful'.
Of the three reasons suggested by the troubleshooter, I
have tried the update with AV (Trend) switched off; I
have oodles of free space on my HDD; and I have tried the
download both connected via my home network and via a
direct ISP connection. All permutations give the same
result. The problem is repeatable.
Anyone else seen this, please? It sounds similar to the
several posts here of the 'Unable to check for updates'
syndrome - fix for which was posted on 11 Nov. at 3:33.
However, the difference here is that the check completes
OK but the detection is obviously wrong! Should I just
uninstall and try again?
Regards,
Ian
Help/About from each product. The product is activated,
but forms part of a Volume Licence arrangement from the
retailer I used (Ramesys in UK).
On attempting Office update from
http://office.microsoft.com/officeupdate/default.aspx,
the 'Check for updates' suggests that I need SP-1 and a
security update for MS Project (KB822211), 6Mb total. All
other updates are greyed out (dependent on SP-1). On
starting the installation, after EULA, confirmation
and 'have your product CD ready' screens, the download
screen appears but then closes very quickly
with 'installation unsuccessful'.
Of the three reasons suggested by the troubleshooter, I
have tried the update with AV (Trend) switched off; I
have oodles of free space on my HDD; and I have tried the
download both connected via my home network and via a
direct ISP connection. All permutations give the same
result. The problem is repeatable.
Anyone else seen this, please? It sounds similar to the
several posts here of the 'Unable to check for updates'
syndrome - fix for which was posted on 11 Nov. at 3:33.
However, the difference here is that the check completes
OK but the detection is obviously wrong! Should I just
uninstall and try again?
Regards,
Ian