"barryn" <> wrote in message news:21819551-FC3B-42D4-A9B2-...
>I have recently had hard drive problems. I installed a new drive,
> partitioned it and copied over my old C & D partitions to the new drive usinf
> the WD Data Lifeguard tools.
> I then switched disks and successfully booted from the new disk.
> However, I have had major problems with Microsoft software including Office
> 2007, Synctoy, Windows 7 Advisor etc.
> Uninstalling Microsoft software results in error messages saying that the
> uninstall info is missing from ...\temp
> For example, Office was being treated as a new installation and produced
> error messages each time I opened Word. I was unable to unistall through the
> control panel and had to uninstall using the Microsoft guidelines. I then
> re-installed Office.
> However, auto software updates will not install - giving an error code
> 0x80070663.
<cmd_output OS="XPsp3">
E:\>set /a c = 0x663
1635
E:\>net helpmsg %c%
This patch package could not be opened. Verify that the patch package
exists and that you can access it, or contact the application vendor
to verify that this is a valid Windows Installer patch package.
</cmd_output>
> I've applied the published solution, checking out the registry,
Registry? This stuff about code pages you mean?
http://social.answers.microsoft.com/...d-50cece0de17d
(Microsoft search for
(0x80070663 OR 80070663) Vista -inurl:communities
)
> but the problem remains.
> I've manually removed Synctoy and Sync Framework etc but still can't
> re-install Synctoy as it says it's corrupted.
> Will upgrading to Vista clear these problems or will they remain as they are
> applications related problems?
Looks like bits of your OS haven't been copied successfully.
So I would think reinstalling it or upgrading it could clean that up.
> Going back to the old drive (if it doesn't crash) and uninstalling prior to
> setting up the new drive is, I feel, unlikely to work as these problems seem
> to be due to Microsoft data not being transfered to the new drive.
> I really don't want to zap the disks and build from new but I'm getting
> desparate for a solution.
> PLEASE HELP !!
This really has more to do with your OS and its maintenance
than with WU, which deals more specifically with how updates
are distributed to independent client machines.
However, I would be curious to get some more details to supplement
your error code. You would do that by finding the context of the code
in any diagnostics the update attempt created or modified.
Additionally you could use ProcMon to see how any other registry and
file accesses related to those diagnostics.
Good luck
Robert Aldwinckle
---