Erik/kbctemp
One thing I noted that when Windows doesn't like the Digispark, it doesn't like it and refuse to acknowedge it.
This includes having it plugged in while data is sent out the pins that are used for USB ...it throws its toys out the cot.!
This wouldn't explain the windows7 machine as well.
Adding it to another port doesn't usually result in success as its recognises the same PID/VIB and usually heads to the same place for the dlls, etc.
Powering your computer down means select shutdown, and when it all goes quiet REMOVE the power plug.
The USB is often powered by the BIOS to enable wake on USB, etc.
You can easily prove this by leaving the Digispark plugged in and seeing if the power led is on when its shut down.
I don't think you'll see the USB power get shut off on a desktop, as they usually have a mains power profile.
Laptop on battery yes, depending on the settings from the manufacturer (or serious user)
None of mine got the power killed when they weren't recognised ..
You can check in ..Windows\inf to see the latest oemxx.inf file (sort by date) and check if there is a corresponding .pnf.
You can open the .inf with notepad and it should include Digispark Bootloader
The .pnf is created when windows recognises the device.
I found deleting them and then running the InstallDriver.exe located in (..wherever you have Digispark IDE..)\Digispark - Windows Driver\directory.
Despite loading a driver, windows still wants to go away and find it via Update.
If you do see it heading off, you can stop it, but like most things microsoft, I'm not sure its a permanent instruction, or how to stop it again.
There are some USBView utilities (windows and linux)on the FTDI website.
http://www.ftdichip.com/Support/Utilities.htm.
It will show a device that windows thinks is not installed correctly, or if it recognises it.
Cheers
Mark