Error Code: 0x80070645

Code@discussions.microsoft.com Error Code

unread,

Feb 3, 2009, 9:15:01 PM2/3/09

to

I tried updating to the new Family Pack 3.5 Framework. This was the what I
received Error Code: 0x80070645 .

Anyone out there know how to fix this?

Thanks for your help.

code too@discussions.microsoft.com error code too

unread,

Feb 4, 2009, 9:58:04 AM2/4/09

to

I am getting this same error code when installing this update. My machine
does have .NET Framework 3.5 SP1 (BETA) installed previously. Working on
figuring out the root of the problem, and I will update here if I do...

opus44

unread,

Feb 4, 2009, 12:32:02 PM2/4/09

to

"Error Code" wrote:

I researched this and came up with this link:
http://support.microsoft.com/kb/923100

I followed the intructions and I fixed the problem for me.

opus44

unread,

Feb 4, 2009, 12:32:03 PM2/4/09

to

code too@discussions.microsoft.com error code too

unread,

Feb 5, 2009, 1:51:35 PM2/5/09

to

I glance at the article that OpusXX mentioned, and it looked similar to the
solution that I figured out.

In "add remove programs" from the control panel, be sure to check the box
that says "display updates". I had a beta version of .NET FW 3.5 installed
previously. I removed that update, rebooted my computer, then installed the
.NET FW 3.5 (most recent and NON BETA) and it all worked.

Hope that helps.

nha

unread,

Feb 7, 2009, 1:24:01 PM2/7/09

to

Hi: I received the same error code, and have tried everything shown. I did
not have 3.5 beta installed, so, as per link someone here posted from
microsoft, I uninstalled all net framework programs on my computer, cosed
out, and then tried to run the indows install cleanup that the link saqid to
download next - but no reference there to any net framework showing to clean
up. So I turned off my machine eyt again, and tried to reinstall all net
framework programs that I'd had on my computer and uninstalled, and found
that I couldn't install even one of those programs. So it now appears I have
no net frameworks on my computer, I can't install or celan up anything, and
am just thorouly lost and confused. I will try to do the last-resort
uninstall (if there's anything left to uninstall) referred to in the windows
article, but I have a feeling I'm in trouble. Any suggestions from anyone?

Rainer

unread,

Feb 8, 2009, 5:34:01 AM2/8/09

to

Hello, I got the same error. No beta installed. Windows Update says that the
product is already downloaded and can be installed. But the install reports
the error, mentioned in the subject, on the Windows Update Page only (no
error code is reported by the local install. The local install only reports
that the install was not successful - no reason mentioned).
How to fix it?
How to change the state: downloaded and ready to install?
How to remove the package from my local PC? or
How to make it work?
BTW - I have searched MS websites the whole morning to find a solution.
Nothing found.
Thank you very much in advance.
Regards, Rainer

unread,

Mar 2, 2009, 11:59:00 PM3/2/09

to

bloody Microsoft must fix this issue in the update itself. Some not so good
programmer messed up and now lots of people have to deal with this bull.

Harry Johnston [MVP]

unread,

Mar 3, 2009, 10:00:49 PM3/3/09

to

mb wrote:

> bloody Microsoft must fix this issue in the update itself. Some not so good
> programmer messed up and now lots of people have to deal with this bull.

I haven't yet seen any evidence that these issues are caused by a fault in the
update rather than existing issues on the affected computers. Be that as it
may, it is unlikely that Microsoft will make any changes to the .NET 3.5
installer at this point.

Harry.

Emily

unread,

Apr 22, 2009, 9:24:23 AM4/22/09

to

I also have this promblem with the same error code. Please if you tell me
what OS details means I will provide them. Please help,
Regards
Emily

Gordonmdlnaim

unread,

May 12, 2009, 11:09:01 PM5/12/09

to

Well, this is not the first time I've had to wrestle with .NET framework
update issues... I'm going to wait a bit on this one before I uninstall the
whole mess and start over like the last time. Something is just not
coordinated properly - it's the only update issue I've ever had, and here it
is again. :(

Jakob Bohm

unread,

May 13, 2009, 7:53:44 AM5/13/09

to

Harry Johnston [MVP] wrote:
> mb wrote:
>
>> bloody Microsoft must fix this issue in the update itself. Some not so
>> good programmer messed up and now lots of people have to deal with
>> this bull.
>
> I haven't yet seen any evidence that these issues are caused by a fault
> in the update rather than existing issues on the affected computers. Be
> that as it may, it is unlikely that Microsoft will make any changes to
> the .NET 3.5 installer at this point.
>
> Harry.
>

Some time ago I also had this (or a very similar) problem on one of my
machines with the "update to .NET framework 3.x", after much debugging I
think I found the reason, and it WAS a Microsoft mistake (though
reporting bugs to Microsoft is always impossible thanks to the PSS idiots):

Even though the update description did not say so, the update downloaded
by Windows Update/Microsoft Update actually contained two complete and
unrelated MSI patches for two different versions of the .NET framework.
If patch#1 is irrelevant or already installed on your computer,
installing patch#1 fails and the stupid, stupid update package then
skips the needed patch#2 and reports that the entire update package
failed to install (with no reporting of the details, just a
HRESULT-wrapped hexadecimal version of a decimal MSI error code). The
next time WU/MU/AU checks for updates it again checks if patch#2 is
needed and not installed, redownloads the two-patch update package, runs
it and fails again and again and again.

So far the only workaround I could find was to uninstall ALL versions of
the .NET framework, reboot, use the ".NET Cleaner" to remove anything
not removed by the uninstall programs, reboot, manually reinstall all
the .NET frameworks and their service packs from full administrative
downloads in whichever sequence bypasses the problem, reboot, rerun
WU/MU, reboot, rerun WU/MU, reboot.

The thing Microsoft could/should do is simply put the two MSI patches
individually on WU/MU/AU (which already supports MSP files directly),
then the fact that each patch is tried on its own and the separation of
the detection for patch#1 and patch#2 should clean up the problem
automagically.

--
Jakob Bøhm, M.Sc.Eng. * j...@danware.dk * direct tel:+45-45-90-25-33
Netop Solutions A/S * Bregnerodvej 127 * DK-3460 Birkerod * DENMARK
http://www.netop.com * tel:+45-45-90-25-25 * fax:+45-45-90-25-26
Information in this mail is hasty, not binding and may not be right.
Information in this posting may not be the official position of Netop
Solutions A/S, only the personal opinions of the author.

Robert Aldwinckle

unread,

May 13, 2009, 10:35:54 AM5/13/09

to

"Gordonmdlnaim" <Gordon...@discussions.microsoft.com> wrote in message
news:619CCE88-4706-437A...@microsoft.com...

> Well, this is not the first time I've had to wrestle with .NET framework
> update issues...

> I'm going to wait a bit on this one before I uninstall the
> whole mess and start over like the last time.

I have found that that is not necessary if you revert to a manual install
*and* you pay attention to the diagnostics it tries to give you if it fails.
In fact, you may find that those same diagnostics are already present
in the logs the install creates; then the only real significant effect of the
manual install is that it highlights the suggested resolution for you.

> Something is just not
> coordinated properly - it's the only update issue I've ever had, and here it
> is again. :(

In my case it was some beta versions of the components it includes
that it wanted me to uninstall first. YMMV.

Good luck

Robert Aldwinckle
---