Support for installing .NET Framework Security updates

July 12, 2007

..NET Framework SP Setup Issues

http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

The above blog > provides a reference to common setup issues and

workarounds for .NET Framework 1.1 Service

> Pack 1 (SP1) and .NET Framework 1.0 Service Pack 3 (SP3).

It does contain error codes for Windows Update, so at least that's a

start in the right direction.

*** Be sure to read ' How to get help ' ***

Then gather the log files and contact Product Support Services for *NO

CHARGE SUPPORT* in getting July's Security updates for .NET Framework

installed.

From : Microsoft Security Bulletin MS07-040 - Critical

Vulnerabilities in .NET Framework Could Allow Remote Code Execution (931212)

http://www.microsoft.com/technet/security/Bulletin/MS07-040.mspx

> Support:

> • Customers in the U.S. and Canada can receive technical support from Microsoft Product

> Support Services at 1-866-PCSAFETY. There is no charge for support calls that are

> associated with security updates.

> • International customers can receive support from their local Microsoft subsidiaries.

> There is no charge for support that is associated with security updates. For more

> information about how to contact Microsoft for support issues, visit the International

> Support Web site. http://go.microsoft.com/fwlink/?LinkId=21155

MowGreen [MVP 2003-2007]

===============

*-343-* FDNY

Never Forgotten

===============

July 13, 2007

look in the newsgroup for George's

SOLUTION to the .net "failed to install" update

"MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message

news:u9GCU1MxHHA.3560@TK2MSFTNGP02.phx.gbl...

> .NET Framework SP Setup Issues

> http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

>

> The above blog > provides a reference to common setup issues and

> workarounds for .NET Framework 1.1 Service

>> Pack 1 (SP1) and .NET Framework 1.0 Service Pack 3 (SP3).

>

> It does contain error codes for Windows Update, so at least that's a start

> in the right direction.

>

> *** Be sure to read ' How to get help ' ***

>

> Then gather the log files and contact Product Support Services for *NO

> CHARGE SUPPORT* in getting July's Security updates for .NET Framework

> installed.

>

> From : Microsoft Security Bulletin MS07-040 - Critical

> Vulnerabilities in .NET Framework Could Allow Remote Code Execution

> (931212)

> http://www.microsoft.com/technet/security/Bulletin/MS07-040.mspx

>

>> Support:

>> • Customers in the U.S. and Canada can receive technical support from

>> Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge

>> for support calls that are associated with security updates.

>> • International customers can receive support from their local Microsoft

>> subsidiaries. There is no charge for support that is associated with

>> security updates. For more information about how to contact Microsoft for

>> support issues, visit the International Support Web site.

>> http://go.microsoft.com/fwlink/?LinkId=21155

>

> MowGreen [MVP 2003-2007]

> ===============

> *-343-* FDNY

> Never Forgotten

> ===============

July 13, 2007

It worked for George, but does it work for everyone ?

MS needs a body count on this issue, Michel. Otherwise they'll say it's

just a small percentage of Users who are experiencing this. <w>

FWIW, all of the .NET updates installed just fine on all of my systems.

Perhaps the problem lies in the original installation being faulty due

to interference from antivirus software. This causes subsequent security

updates to fail.

Or, perhaps folks run 'registry cleaners' that delete needed

information|setup files for said updates to install properly.

Quien sabe ?

MowGreen [MVP 2003-2007]

===============

*-343-* FDNY

Never Forgotten

===============

realcestmoi wrote:

> look in the newsgroup for George's

> SOLUTION to the .net "failed to install" update

>

> "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message

> news:u9GCU1MxHHA.3560@TK2MSFTNGP02.phx.gbl...

>

>>.NET Framework SP Setup Issues

>>http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

>>

>>The above blog > provides a reference to common setup issues and

>>workarounds for .NET Framework 1.1 Service

>>

>>>Pack 1 (SP1) and .NET Framework 1.0 Service Pack 3 (SP3).

>>

>>It does contain error codes for Windows Update, so at least that's a start

>>in the right direction.

>>

>>*** Be sure to read ' How to get help ' ***

>>

>>Then gather the log files and contact Product Support Services for *NO

>>CHARGE SUPPORT* in getting July's Security updates for .NET Framework

>>installed.

>>

>>From : Microsoft Security Bulletin MS07-040 - Critical

>>Vulnerabilities in .NET Framework Could Allow Remote Code Execution

>>(931212)

>>http://www.microsoft.com/technet/security/Bulletin/MS07-040.mspx

>>

>>>Support:

>>>• Customers in the U.S. and Canada can receive technical support from

>>>Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge

>>>for support calls that are associated with security updates.

>>>• International customers can receive support from their local Microsoft

>>>subsidiaries. There is no charge for support that is associated with

>>>security updates. For more information about how to contact Microsoft for

>>>support issues, visit the International Support Web site.

>>>http://go.microsoft.com/fwlink/?LinkId=21155

>>

>>MowGreen [MVP 2003-2007]

>>===============

>> *-343-* FDNY

>>Never Forgotten

>>===============

>

July 13, 2007

In news:%23rxpQSXxHHA.3720@TK2MSFTNGP02.phx.gbl,

MowGreen [MVP] <mowgreen@nowandzen.com> wrote:

.........

>

> FWIW, all of the .NET updates installed just fine on all of my

> systems. ......

Same here. But I do admit that every time MS releases a .NET update via

WU/MU we have a massive influx of failed notices in this and related

newsgroups.

I'm starting to think that all .NET updates need to be treated like a

service pack, where they are downloaded and installed offline rather than

being pushed/streamed via WU/MU/AU.

....Sky

July 13, 2007

Sky King wrote:

>

> In news:%23rxpQSXxHHA.3720@TK2MSFTNGP02.phx.gbl,

> MowGreen [MVP] <mowgreen@nowandzen.com> wrote:

> ........

>

>>

>> FWIW, all of the .NET updates installed just fine on all of my

>> systems. ......

>

> Same here. But I do admit that every time MS releases a .NET update via

> WU/MU we have a massive influx of failed notices in this and related

> newsgroups.

>

> I'm starting to think that all .NET updates need to be treated like a

> service pack, where they are downloaded and installed offline rather

> than being pushed/streamed via WU/MU/AU.

>

> ...Sky

>

There must be *some* commonality for why there are so many issues

installing these and other .NET updates.

Perhaps I'm naive ? <w>

MowGreen [MVP 2003-2007]

===============

*-343-* FDNY

Never Forgotten

===============

July 13, 2007

MowGreen [MVP] wrote:

> Sky King wrote:

>>> FWIW, all of the .NET updates installed just fine on all of my

>>> systems. ......

>>

>> Same here. But I do admit that every time MS releases a .NET update via

>> WU/MU we have a massive influx of failed notices in this and related

>> newsgroups.

>>

>> I'm starting to think that all .NET updates need to be treated like a

>> service pack, where they are downloaded and installed offline rather

>> than being pushed/streamed via WU/MU/AU.

>>

> There must be *some* commonality for why there are so many issues

> installing these and other .NET updates.

> Perhaps I'm naive ? <w>

I suspect the Fickle Finger of Fate will end up pointing to real-time

protection by anti-virus, anti-spyware, and/or third-party firewall.

--

~PA Bear

July 14, 2007

"PA Bear" <PABearMVP@gmail.com> wrote in message

news:eLgdqQZxHHA.4300@TK2MSFTNGP04.phx.gbl...

| MowGreen [MVP] wrote:

| > Sky King wrote:

| >>> FWIW, all of the .NET updates installed just fine on all of my

| >>> systems. ......

| >>

| >> Same here. But I do admit that every time MS releases a .NET update via

| >> WU/MU we have a massive influx of failed notices in this and related

| >> newsgroups.

| >>

| >> I'm starting to think that all .NET updates need to be treated like a

| >> service pack, where they are downloaded and installed offline rather

| >> than being pushed/streamed via WU/MU/AU.

| >>

| > There must be *some* commonality for why there are so many issues

| > installing these and other .NET updates.

| > Perhaps I'm naive ? <w>

|

| I suspect the Fickle Finger of Fate will end up pointing to real-time

| protection by anti-virus, anti-spyware, and/or third-party firewall.

| --

| ~PA Bear

|

I forgot to turn off all the above, anti-virus, anti-spyware, 3rd party firewall,

WinPatrol, you name it I left it all on.

No problems.

I did note however during installation my security did pop up to ask me to allow

installation and WinPatrol did ask about a service which I allowed at the time because I

knew what was happening. Perhaps some security software, just stops the installation

process altogether without warning.

--

====================================

TaurArian [MS-MVP] 2005-2008 - Australia

====================================

How to make a good post: http://www.dts-l.org/goodpost.htm

Defending your machine: http://defendingyourmachine2.blogspot.com/

http://taurarian.mvps.org/index.htm

Emails will not be acknowledged - please post to the newsgroup so all may benefit.

July 14, 2007

TaurArian [MS-MVP] wrote:

> "PA Bear" <PABearMVP@gmail.com> wrote in message

> news:eLgdqQZxHHA.4300@TK2MSFTNGP04.phx.gbl...

>> MowGreen [MVP] wrote:

>>> Sky King wrote:

>>>>> FWIW, all of the .NET updates installed just fine on all of my

>>>>> systems. ......

>>>>

>>>> Same here. But I do admit that every time MS releases a .NET update

>>>> via

>>>> WU/MU we have a massive influx of failed notices in this and related

>>>> newsgroups.

>>>>

>>>> I'm starting to think that all .NET updates need to be treated like a

>>>> service pack, where they are downloaded and installed offline rather

>>>> than being pushed/streamed via WU/MU/AU.

>>>>

>>> There must be *some* commonality for why there are so many issues

>>> installing these and other .NET updates.

>>> Perhaps I'm naive ? <w>

>>

>> I suspect the Fickle Finger of Fate will end up pointing to real-time

>> protection by anti-virus, anti-spyware, and/or third-party firewall.

>> --

>> ~PA Bear

>>

>

> I forgot to turn off all the above, anti-virus, anti-spyware, 3rd party

> firewall, WinPatrol, you name it I left it all on.

> No problems.

> I did note however during installation my security did pop up to ask me to

> allow installation and WinPatrol did ask about a service which I allowed

> at

> the time because I knew what was happening. Perhaps some security

> software,

> just stops the installation process altogether without warning.

Well, certainly not all AV & anti-spyware apps and/or third-party firewalls,

but...

I've seen threads here and posts elsewhere stating that disabling, e.g.,

CounterSpy and/or ZA allowed the MS07-040 updates to install without a

hitch.

--

~PA Bear

July 14, 2007

Useless to me. I don't even have .NET 1.0 installed and this damned SP3

update keeps getting shoved in my face. Then it fails with 8007F070,

which isn't mentioned on that site anywhere.

MowGreen [MVP] wrote:

> .NET Framework SP Setup Issues

> http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

July 14, 2007

Installed on my system with no problems and I never turn off my AV or ZA

for any update.

Joan

PA Bear wrote:

> MowGreen [MVP] wrote:

>> Sky King wrote:

>>>> FWIW, all of the .NET updates installed just fine on all of my

>>>> systems. ......

>>>

>>> Same here. But I do admit that every time MS releases a .NET

>>> update via WU/MU we have a massive influx of failed notices in this

>>> and related newsgroups.

>>>

>>> I'm starting to think that all .NET updates need to be treated like

>>> a service pack, where they are downloaded and installed offline

>>> rather than being pushed/streamed via WU/MU/AU.

>>>

>> There must be *some* commonality for why there are so many issues

>> installing these and other .NET updates.

>> Perhaps I'm naive ? <w>

>

> I suspect the Fickle Finger of Fate will end up pointing to real-time

> protection by anti-virus, anti-spyware, and/or third-party firewall.

July 15, 2007

Hi there mister or Mrs .,

Might be usefull to tell whis OS you are running as Sp3 can be a windows

2000 service pack or Ofiice Sp3)

Best regards,

Michel Denie

"·" <noreply@all.com> wrote in message

news:uk$gbVkxHHA.3684@TK2MSFTNGP02.phx.gbl...

> Useless to me. I don't even have .NET 1.0 installed and this damned SP3

> update keeps getting shoved in my face. Then it fails with 8007F070,

> which isn't mentioned on that site anywhere.

>

> MowGreen [MVP] wrote:

>

>> .NET Framework SP Setup Issues

>> http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

>

July 15, 2007

· wrote:

> Useless to me. I don't even have .NET 1.0 installed and this

> damned SP3 update keeps getting shoved in my face. Then it fails

> with 8007F070, which isn't mentioned on that site anywhere.

If you need help with the SP3 stuff - well - most likely you need to locate

your Office XP CD and put it in before you attempt the update. I say this

assuming you have Office XP and not Windows 2000 - another possibility.

Also - something *could* be awry with your WU...

Try one (or both) of these:

Solution to try (1):

Get Dial-a-Fix:

http://wiki.djlizard.net/Dial-a-fix

Use its options to fix Windows Installer, fix Windows Update, and all the

Registration Center options.

Turn off the "Empty System32\Catroot 2"

Then click "GO"

Do NOT do "Flush SoftwareDistribution".

Solution to try (2):

1) Reboot and logon as a user with Administrative Privs...

2) Immediately run the following batch script (You will have to create it by

cutting/pasting as directed.)

- Click Start, Run, type: notepad C:\register.bat and press Enter. Choose

Yes when you are prompted.

- Copy the following commands and then paste them into the opened Notepad

window:

regsvr32 comcat.dll /s

regsvr32 shdoc401.dll /s

regsvr32 shdoc401.dll /i /s

regsvr32 asctrls.ocx /s

regsvr32 oleaut32.dll /s

regsvr32 shdocvw.dll /I /s

regsvr32 shdocvw.dll /s

regsvr32 browseui.dll /s

regsvr32 browseui.dll /I /s

regsvr32 msrating.dll /s

regsvr32 mlang.dll /s

regsvr32 hlink.dll /s

regsvr32 mshtmled.dll /s

regsvr32 urlmon.dll /s

regsvr32 plugin.ocx /s

regsvr32 sendmail.dll /s

regsvr32 scrobj.dll /s

regsvr32 mmefxe.ocx /s

regsvr32 corpol.dll /s

regsvr32 jscript.dll /s

regsvr32 msxml.dll /s

regsvr32 imgutil.dll /s

regsvr32 thumbvw.dll /s

regsvr32 cryptext.dll /s

regsvr32 rsabase.dll /s

regsvr32 inseng.dll /s

regsvr32 iesetup.dll /i /s

regsvr32 cryptdlg.dll /s

regsvr32 actxprxy.dll /s

regsvr32 dispex.dll /s

regsvr32 occache.dll /s

regsvr32 occache.dll /i /s

regsvr32 iepeers.dll /s

regsvr32 urlmon.dll /i /s

regsvr32 cdfview.dll /s

regsvr32 webcheck.dll /s

regsvr32 mobsync.dll /s

regsvr32 pngfilt.dll /s

regsvr32 licmgr10.dll /s

regsvr32 icmfilter.dll /s

regsvr32 hhctrl.ocx /s

regsvr32 inetcfg.dll /s

regsvr32 tdc.ocx /s

regsvr32 MSR2C.DLL /s

regsvr32 msident.dll /s

regsvr32 msieftp.dll /s

regsvr32 xmsconf.ocx /s

regsvr32 ils.dll /s

regsvr32 msoeacct.dll /s

regsvr32 inetcomm.dll /s

regsvr32 msdxm.ocx /s

regsvr32 dxmasf.dll /s

regsvr32 l3codecx.ax /s

regsvr32 acelpdec.ax /s

regsvr32 mpg4ds32.ax /s

regsvr32 voxmsdec.ax /s

regsvr32 danim.dll /s

regsvr32 Daxctle.ocx /s

regsvr32 lmrt.dll /s

regsvr32 datime.dll /s

regsvr32 dxtrans.dll /s

regsvr32 dxtmsft.dll /s

regsvr32 WEBPOST.DLL /s

regsvr32 WPWIZDLL.DLL /s

regsvr32 POSTWPP.DLL /s

regsvr32 CRSWPP.DLL /s

regsvr32 FTPWPP.DLL /s

regsvr32 FPWPP.DLL /s

regsvr32 WUAPI.DLL /s

regsvr32 WUAUENG.DLL /s

regsvr32 ATL.DLL /s

regsvr32 WUCLTUI.DLL /s

regsvr32 WUPS.DLL /s

regsvr32 WUWEB.DLL /s

regsvr32 wshom.ocx /s

regsvr32 wshext.dll /s

regsvr32 vbscript.dll /s

regsvr32 scrrun.dll mstinit.exe /setup /s

regsvr32 msnsspc.dll /SspcCreateSspiReg /s

regsvr32 msapsspc.dll /SspcCreateSspiReg /s

regsvr32 /s urlmon.dll

regsvr32 /s mshtml.dll

regsvr32 /s shdocvw.dll

regsvr32 /s browseui.dll

regsvr32 /s jscript.dll

regsvr32 /s vbscript.dll

regsvr32 /s scrrun.dll

regsvr32 /s msxml.dll

regsvr32 /s actxprxy.dll

regsvr32 /s softpub.dll

regsvr32 /s wintrust.dll

regsvr32 /s dssenh.dll

regsvr32 /s rsaenh.dll

regsvr32 /s gpkcsp.dll

regsvr32 /s sccbase.dll

regsvr32 /s slbcsp.dll

regsvr32 /s cryptdlg.dll

regsvr32 /s schannel.dll

regsvr32 /s oleaut32.dll

regsvr32 /s ole32.dll

regsvr32 /s shell32.dll

regsvr32 /s initpki.dll

regsvr32 /s msscript.ocx

regsvr32 /s dispex.dll

regsvr32 jscript.dll /s

del %temp% /Q /F

net stop wuauserv

net stop cryptsvc

ren %windir%\system32\catroot2 catroot2.old

cd /d %windir%\SoftwareDistribution

rd /s DataStore /Q

regsvr32 wuapi.dll /s

regsvr32 wups.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wucltui.dll /s

regsvr32 wuweb.dll /s

regsvr32 msxml.dll /s

regsvr32 msxml2.dll /s

regsvr32 msxml3.dll /s

regsvr32 urlmon.dll /s

net start cryptsvc

net start wuauserv

exit

- After you paste the above commands, please close the Notepad window.

Choose Yes when you are prompted to save the file.

- Click Start, Run, type:

C:\register.bat and press Enter to run the commands I have pasted.

The Process may take sometime.

3) Download/Install Windows Update v3.

http://go.microsoft.com/fwlink/?LinkID=91237

(You may need to install it using the command line switch "/wuforce" right

after an additional reboot - immediately after logging in.)

4) Download/Install the 927891 patch.

http://www.microsoft.com/downloads/details.aspx?FamilyId=7A81B0CD-A0B9-497E-8A89-404327772E5A

5) Reboot.

If you need help with the .NET Framework stuff:

(1) You need to repair .NET Framework 1.1 - obliterating all remnants of it

and installing it/patching it fully.

How to troubleshoot Microsoft .NET Framework 1.1 installation issues

http://support.microsoft.com/kb/824643

- Unregister and then reregister Windows Installer (See article)

- Manually remove and then reinstall the .NET Framework 1.1 (See Article)

For the articles below, follow the "IT professionals" link and find the

download for your OS.

- Download/Install http://support.microsoft.com/kb/867460/

- Download/Install http://support.microsoft.com/kb/886903/

- Download/Install http://support.microsoft.com/kb/928366/

Reboot as needed and at the end.

(2) You need to repair .NET Framework 2.0 - obliterating all remnants of it

and installing it/patching it fully.

How to troubleshoot Microsoft .NET Framework 2.0 installation issues

http://support.microsoft.com/kb/908077/

- Unregister and then reregister Windows Installer (See article)

- Manually remove and then reinstall the .NET Framework 2.0 (See Article)

For the articles below, follow the "IT professionals" link and find the

download for your OS.

- Download/Install http://support.microsoft.com/kb/917283/

- Download/Install http://support.microsoft.com/kb/922770/

- Download/Install http://support.microsoft.com/kb/928365/

Reboot as needed and at the end.

(3) You need to repair .NET Framework 3.0 - obliterating all remnants of it

and installing it/patching it fully.

Unfortunately - there is no particular article pertaining to .NET Framework

3.0 that I could find. I have not had issues, however, just going into the

Control Panel --> Add or Remove Programs and just locating/removing it and

its patches. I suggest you do the same and then reboot...

Download/install using this distributable package:

http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en

Reboot as needed and at the end.

(4) Cleanup your updates system...

Get Dial-a-Fix:

http://wiki.djlizard.net/Dial-a-fix

Use its options to fix:

- Windows Installer

- Windows Update

- All the Registration Center options

Turn off the "Empty System32\Catroot 2"

Do NOT do "Flush SoftwareDistribution".

Then click "GO"... May take a while.

Reboot when it is done...

(5) Visit http://windowsupdate.microsoft.com/ and scan for updates. Choose

the critical updates you need and install them. Do not bother getting

hardware updates (unless you happen to have some Microsoft hardware

installed) and "Optional Updates" are *usually* just what the name infers -

but feel free to see if you want any of the "Optional" ones.

(6) Come back here and let us know how you faired.

--

Shenan Stanley

MS-MVP

--

How To Ask Questions The Smart Way

http://www.catb.org/~esr/faqs/smart-questions.html

Sign In

Support for installing .NET Framework Security updates

Recommended Posts

Guest MowGreen [MVP]

Guest realcestmoi

Guest MowGreen [MVP]

Guest Sky King

Guest MowGreen [MVP]

Guest PA Bear

Guest TaurArian [MS-MVP]

Guest PA Bear

Guest ·

Guest Joan Archer

Guest realcestmoi

Guest Shenan Stanley

Browse

Activity