I was thinking that was the case. A rebuild is in order because my restore
points are not even working right.
Thanks for checking!
"Patrick Schmid" wrote:
.net framework 3 messed up your system?
You might want to consider a system restore prior to the point of
installing it.
Patrick Schmid
--------------
http://pschmid.net
"Mike H." wrote in message
:
Another interesting find, so this may not just be Word 2007 related. When I
open up wordpad on the computer it too begins using a large amount of memory
and then closes without warning or errors.
Any ideas?
"Mike H." wrote:
I have been using Beta 2 of Microsoft Office since it was made available with
no issues. Yesterday I saw there was one critical and a few optional
updates for Windows XP. I went ahead and installed them. I also grabbed
the latest .NET Framework 3.0 to play with. Everything seemed to work fine
after the updates. Last night I tried to edit a word document in Word 2007
B2. After about 10 - 20 seconds Word just closed. I tried again and same
thing happened.... no error message, it just closes. I gave up working on
the document and called it a night.
This morning I have been doing some digging. If I open up task manager and
launch Word I see the winword.exe process start up. The memory usage
climbes to about 50Mb and holds for a few seconds... it then starts climbing
up to about 260Mb and then Word closes.
I decided that maybe the .NET 3.0 framework screwed something up, so I
uninstalled. Still no luck... still seeing the memory issue / crash with
Word.
I have tried repairing, removing and resinstalling word but none of that
seems to resolve the issue. This is very strange since it has been working
so well up until last night.
I even went so far as to uninstall the windows updates to see if that makes
a difference. Nope... still same memory leak issue.
Anyone else seeing this? Any ideas on how I can fix this? I would hate
to roll back to Office 2003.