.NET Framework update preventing standby

  • Thread starter Thread starter krisbke
  • Start date Start date
I'm so glad to find out that I'm not the only one having this problem. I
don't have a clue how to disable this program, and would like to remove the
entire update IF it wouldn't harm my computer.

Any suggestions?

"krisbke" wrote:

> Hi there.
>
> Since yesterday's updates, I'm unable to put my computer into standby. When
> I flip the lid open again, there's a message saying 'Microsoft .NET Framework
> v1.1.4322 Update' prevented it going into standby. It also says I should
> disable the service. Clearly, I can do that and I imagine it would work, but
> is there another solution? If not, how important is this update and what
> would I lose by not having it running?
>
> I'm using XP Home SP2 on an HP Pavilion dv5000 and would be glad to give any
> other useful info.
>
> Thanks for your help with this, if anyone knows what is going on!
 
I know this is no fix but if you want to go into standby while we wait
for the geniuses at Microsoft to fix this hit Ctrl-Alt-Del and end the
netfixupdate.exe and then you will go into standby. But Its probably
better to shut down until this gets fixed.


--
Randlemen
------------------------------------------------------------------------
Randlemen's Profile: http://forums.techarena.in/member.php?userid=28007
View this thread: http://forums.techarena.in/showthread.php?t=781644

http://forums.techarena.in
 
OK guys, I got mine to work. The person helping me via microsoft support is
still not addressing the actual issue of the standby problem, but I simply
followed her instruction and it worked. I think the culprit is using windows
update to get the KB928366 security update. Her instructions gave an actual
manual download for it, and that is the differece for me. Here they are:

ALSO, BEFORE YOU START, DISABLE ALL ANTIVIRUS, ANTISPYWARE, ANTI WHATEVER
SOFTWARE, HIPS, SOFTWARE FIREWALLS (short of the windows firewall) etc.

1) Either use the add/remove function in the control panel to rid yourself
of all .NET stuff, or use the installer cleanup utility

http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe

2) Run this utility to super clean the lovely KB928366 p.o.s. of an update

http://www.microsoft.com/downloads/...33-0343-4EE4-B0C4-97BD16967A09&displaylang=en

Now, if you have a 32 bit machine, which you likely do, use the last
download link entitled Cleanup-x86.exe. Why it's not entitled x32.exe is
beyond me, but this is Microsoft we are dealing with!

3) Install the .NET framework 1.1

http://download.microsoft.com/download/a/a/c/aac39226-8825-44ce-90e3-bf8203e74006/dotnetfx.exe

4) Install the .NET framework service pack 1

http://download.microsoft.com/downl...-bdb8-c4e00af5b94b/NDP1.1sp1-KB867460-X86.exe

5) MANUALLY install the DREADED stupid p.o.s. security update that we all
would like to shoot with my new trail boss 44 magnum

http://www.download.windowsupdate.c..._20112ef50011e0de2c0e3378139245d81a178b15.exe

ALSO, BEFORE YOU START, DISABLE ALL ANTIVIRUS, ANTISPYWARE, ANTI WHATEVER
SOFTWARE, HIPS, SOFTWARE FIREWALLS (short of the windows firewall) etc.
 
Hi guys,

there is one solution that might help. It is a workaround not a patch. So
the workaround is to stop the .Net service and make it start manually.
This solved my misery for now. Although for some of you this might be a
problem due to some application requiring .Net to start automatically
 
Solution!

For me, anyway, and hopefully for everyone else. I stumbled across an answer
someone better with computers than me posted elsewhere, and perhaps the thing
we all have in common is we use Avira Antivir anti-virus... This link from
their forum provides further links for how to address the issue:

http://forum.antivir.de/thread.php?threadid=24535

This worked for me, the .Net Framework v1.1.4322 Update finished doing its
thing, no longer appears in my list of Services and my computer can now go
into standby. If you do not use Avira Antivir, maybe other anti-virus
programs have the same effect and you should check out the link and follow
the instructions as they apply to you.

Glad to get that sorted!

"rnayden" wrote:

> Hi guys,
>
> there is one solution that might help. It is a workaround not a patch. So
> the workaround is to stop the .Net service and make it start manually.
> This solved my misery for now. Although for some of you this might be a
> problem due to some application requiring .Net to start automatically
 
You must log in or register to reply here.
Back
Top