I had a problem with Windows 7 32 bit Pro serice pack 1 with several icon shortcuts in Classic mode causing Win 7 to force off several items during shutdown. Then it automatically removed several icons from the desktop and everything was ok. (New "C" drive). Also doesn't automatically present menu during install of old applications to install in "XP-3 mode". There were also some conflicts with Realtek sound drivers.
JJK

You know, I've been hearing reports that Windows Service packs have caused severe problems all the way back to Win XP SP1 - and cannot remember having a single problem as a result of a Service Pack upgrade. Needless to say, my Win 7 SP1 / Vegas 10.0c works just fine.

...Jerry

Good to hear.
The reason why I installed SP1 without expecting anything evil was that I also never had any troubles with SP-1-2-3 before.

Here, however, I just had to power-switch-kill one more hang.

Then I tried to restore - but: Error error error: Windows could not restore.

Well - do not cry, I thought - so I just went on editing....
after 6 minutes another hang.... time to find the last full C-drive backup, I think.

Btw John: also good to hear that you could install the SP1 on 6 machines. Here I tried on 5, but only succeded on 2. On the other 3 SP1 stopped in the installation process: Error file xxx missing. Beeing an old IT engineer I tried for a full day googling and trying all the hints - even downloaded the full SP1 - but it would not install.

One of the machines was a brand new, just opened, Eee Pc 1215PN with a fresh and unharmed Genuine Windows 7 Home edition.... and even there SP1 refused to install.

I installed SP1 on Win 7 64 bit two days ago. So far no problems.

me too, so far no probs on 3 machines, 2 with Vegas

/Ulf

No problems here with Windows 7 Pro 64bit and SP1. Like a previous poster I have had no problems with any of the Service Packs from XP onward (although I skipped Vista).

I have an occasional problem that sounds much like yours that already existed before I installed SP1 into my Windows 7 64 bit machine, and still comes up from time to time after.

On my system, it seems to be related to the Internet Browser and some sort of script that some websites run. I have run into this mainly with Firefox, but also with Internet Explorer when I switched to avoid this problem. The symptoms are that Windows just hangs and won't do anything for a period of several minutes. Nothing at all. The mouse will move but that is all. I can't click on anything. Nothing responds. Then after a few minutes it will come back. Sometimes it will go through this over and over again. Reboot and it will come back again every so often. Just maddening.

Anyway, what seems to fix it is to clear my Internet browser cache. What seems to be going on is that some script starts to run, gets stuck, and holds up the whole computer. How a script like this will run from my cache is beyond my understanding, but I know that it is.

Anyway, my guess is that you just ran into this after you updated and the fact that you had updated just before you first ran into this is just a coincidence.

Try clearing your Internet cache and see if that helps. Maybe your problem is different. I'd be really interested to know if this helps.

Hmmm... I did not even realize there was an SP1 until I read this thread. I checked my system and SP1 is installed, so I must have installed it whenever it came out via Windows Update.

My computer is on 24/7. The only times I ever reboot is when I install some new software that insists on rebooting.

No problems here. I know that does not help you, but I just wanted to point out that whatever problems you have may stem from something on your system being incompatible with SP1, and not from SP1 itself.

Gentlemen, gentlemen, thank you:

When so many reported that SP1 worked well on your machines - and nobody had similiar problems - I had to think a second time.

Now what happened else when I installed the SP1?... nothing?? ... no? ... ah well, yes: My son-in-law mailed me some pictures via a thing called Dropbox - and I had to install a small interface program in order to read them.
No big deal? well obviously it was: the little program starts at Windows startup - so I thought: could it be the culprit? - well, I uninstalled Dropbox and restarted Windows - and now I have been editing some hours without any problems.
Right now a New Deshake of some 100 AVCHD clips is humming in the background - a render in running too - and I am editing in foreground with a third instance og Vegas.

I really had forgotten that little Dropbox-thing - and good, that I was persuaded to check a second time when you reported: no problems.

Thank you all...
... and I am ready to be at receiving end for some flaming because of my faux pas, of course.

Yeah, I removed dropbox because it was affecting windows performance. It tries to stay synced.

Glad you figured it out because I have not had any problems with SP1 either.

Dave T2

I'm glad you got it resolved.

No problem with Dropbox here. I love it and use it all the time.

Two non-videoediting software products I've learned about in this forum are Dropbox & Snagit. I love this combo - they work great together!

...Jerry

PS: I forgot who recommended them, but Thank You!!

I had problems with mine blue screening when I let it hibernate. Did a restore point and had no problems afterwards. It restored to right before the SP1 installed without issue.

Glad you got the system running smoothly again. A little diagnosing is good to keep the mind sharp. I'l try to keep the flaming to a minimum.

Here is the way I manage upgrades. I rarely shoot those kinds of bugs on my machines. Unfortunately, where johnmeyer is the IT manager for the Monterey Pennisula, I sometimes think I have been elected for the Central Valley.

From a post in December. It could have been ten years ago or fifteen...

"My approach to keeping it "clean" is that I save an unblemished image of the system with Ghost 15 at every step without ever running software. I have done the same since Drive Image 1 or so. When I want to try a new piece of software, I install a pristine image of the system, install the software, save the image of the freshly installed software, use it and abuse it keeping notes about any configuration changes that I make along the way. When I'm satisfied that I want to keep the software, I install a fresh copy of the image, make the configuration changes and save the image as the "production" image. I keep multiple versions available. Occasionally, I revert to an earlier image than the most current. (I recently had a problem while running Vegas 10.0a and reverted to 9.0e long enough to finish a project. Now, I'm back to running both. About every six weeks, I load a fresh copy of the image, install maintenance from the vendors and create a new gold standard image. I let updates install along the way but they don't become permanent until I reload the image, install and save."

I think with SP1 M$ shows us again their evil face :-) Back to the roots or better, the customer is the beta tester. My editing machine can not install SP1, every time I try I get different error codes. Pretty wild ones....
At work I have three Win7 machines and all come up with different error codes. These machines are OEM Dell boxes so it's not just an issue with custom built systems. Love M$, thanks Bill.

On my machine W7-64bit, things actually improved with Vegas 10c after installing SP1...although I can't be sure if it was the clean un-install/install of Vegas that did more of the trick than SP1.
But, anyway, running SP1 here without any issues, and, relatively stable now....only one crash since....phew !

@darg ranting on about "evil face": It's just not true, mate. I think your slip is showing. If you'd confined your comments to genuine error reports and taken the trouble to inform yourself and diagnose issues before another gratuitous slander, we'd take you more seriously.

W7 SP1 was *extensively* tested and beta'd before release, as any knowledgable forumite can corroborate. As an aside, I've installed W7 SP1 on 5 machines at home (2 x x64, 3 x X86) - all installations were flawless and the machines purr long better than ever.

Perhaps it's best you (a) reset the anti-MS animus, and (b) start again a with a fresh install, and (c) make sure you keep crapware off your system. I'll wager ten to one that your problems (if indeed they are real) are not caused by SP1 or W7, but by the duff drivers, leaky third-party code that ignores WIndows programming guidelines, and a good dose of operator ignorance exacerbated by prejudice.

Back to topic.