Vista x64 SP1

[Catamer]

sorry to bring up this subject again, I know I complained about Vista SP1 before.

I had installed SP1 quite some time ago and it blew up keyclone so that it no longer would maximize wow. the non-maximized windows would not send the keystrokes to the other copies of wow.
I ended up uninstalling SP1 and all of my problems went away. About a month ago SP1 was auto installed because I wasn't paying attention 8| when I allowed windows update to install SP1 but it seemed to work fine.
SP1 was working and I accepted that they must have fixed whatever the problem was.

After 30 days of using SP1 and not having any problems all of my SP1 issues returned with a vengence. :cursing:
I couldn't run keyclone or it would take some 60 seconds for it to start. many programs like IE wouldn't start either.
When I logon to the machine after a cold boot it would take 2 minutes for the welcome center to pop-up.

I uninstalled SP1 again and all of my issues disappeared, the welcome center pops up immediately, keyclone and the maximizer all work fine and I have almost instant program starts.
My only real problem is that I wasted 3 hours checking for all other prossible problems ( full chkdsk, full memory checks, redownload keyclone, etc ) before removing SP1.

[Sarduci]

I've been running 64 bit SP1 for 8 months now. No issues other than the same issues I have on XP with keyclone.

Maybe listing your issues instead of just blaming SP1 would give us somewhere to start.

[mikekim]

how odd, both my multibox machines are Vista64 SP1. the Ultimate Edition machine I upgraded to SP1, and the Home Premium came as SP1 on the OEM disk.

no issues with Keyclone, or starting up

[Rin]

I run Vista Ultimate x 64-bit, sp1 on all 5 of my computers. Each of the machines runs with 8 GBs/RAM, nvidia graphics card (don't have the number offhand)... I haven't encountered any problems yet.

[Catamer]

err.... I thought I did list the issues.
1. keyclone maximizer quit working
2. keyclone won't send keystrokes to un-maximized windows because it never finished properly initializing the windows.
3. programs would not start or take 60-120 seconds to start
3a this include the simple welcome center after a cold boot
3b this included internet explorer
3c this include keyclone

Like I said, I used SP1 for 1 month after the last install and none of the above issues were there.
I rebooted the machine and no-change
I did a full chkdsk and rebooted the machine no-change
I did a vista memory check and rebooted, no-change
I removed SP1 ( a 30-40 min process I might add ) and all is wonderful again.

a a side note, I have 3 PC and the problem didn't show up on all of them this time. my first pass at SP1 it did cause problems on all three machines.

[Bovidae]

When I accidentally let Windows Update add SP1, my mobo fried the same day. Coincidence????

[Thulos]

I've been running Vista 64 SP1 on my boxing machine for months now. I've also been running vista 64 SP1 on many of our work machines with absolutely zero problems.
When I accidentally let Windows Update add SP1, my mobo fried the same day. Coincidence????Yes.

[Vyndree]

What's interesting is that he's uninstalled SP1 two times -- and in both times he was then unable to reproduce the issues he laid out.

I'm curious -- would you mind doing some more tests by intentionally installing SP1 and seeing if you are able to reproduce the issues? Then intentionally uninstall and see if you can repro again? That way we can minimize any after-effects of the other tests/modifications you did prior to uninstalling/reinstalling SP1.

If you can get a really solid repro, I can see what I can do to report the issue to the appropriate groups. Of course, you might not want to waste your time but as a tester I like intriguing issues like these. ;)

[oxxo]

When I accidentally let Windows Update add SP1, my mobo fried the same day. Coincidence????

Yes.

[Fleecy]

Yes!
When I accidentally let Windows Update add SP1, my mobo fried the same day. Coincidence????

[offive]

When I accidentally let Windows Update add SP1, my mobo fried the same day. Coincidence????

Yes, but only if you did the upgrade that ends on a day that doesn’t end with a Y. If the upgrade was done on a day that ends with a Y, then NO your mother board was slated for termination on that day that ends in Y when it detected a new operating system.

You should try Windows Mojave, I hear its hardware neutral, unless you run it on an iPhone then it will brick it.

:D

[Catamer]

I just rebuilt my Vista x32 machine and used a brand spanking new cope of Vista x64 ultra which included SP1.
This machine works wonderfully, I really like it :P . I see they removed the ability to disable UAC from the control panel, it's a pity I know where to disable it in the registry :whistling:

I guess my problems with SP1 are related to the upgrade, maybe I should rebuild that old x64 machine from scratch too.

[Griznah]

I love my Vista64 SP1. Nearly no troubles at all. Using Ultimate.

[aulrich]

I need to hijack the thread a little bit

Both of my vista machines have insane mouse issues, it happens ingame and out of game but i'll mouse over something and my mouse can shoot to the other side of the screen. I also have the while running I'll find myself spinning and looking up. In the past I tried to fix it but nothing posted seemed to work, can someone point me in the direction of the fix.

[Catamer]

are you using any dual boxing software like keyclone, etc?

I used to use one of the freeware packages (for the life of my I can't remember which one) and that was one of it's "features", spining wildly and looking up at the sky.
I now use keyclone and I don't have that spinning problem since then, i'm sure there is other software that doesn't cause the spinning as well.
The problem was not Vista but the software I was using to send keystrokes and mouse clicks to other windows.

[aulrich]

I use multiplicity, but the problem exists in single seat mode to.