I am just re-installing all my games etc onto my new PC.
Just installed SB Pro,inserted the Codemeter stick and windows 7 is giving me a choice...
'Do you want to scan and fix CODEMETER(F:)?
1-Scan and fix (recommended)
2-Continue without scanning.
As far as I am aware it was running fine on my old system.Bearing in mind I once had the stick go faulty on me I don't want to risk another problem.
What shall I do guys?
Many thanks.

i choose #2 Continue without scanning.

i choose that because i am fairly certain that there is nothing that needs fixed on the dongle.

you say it worked fine on your previous OS, so that would make me think that the option to scan the dongle is something new in Windows 7. it does not mean that there is really something wrong with the dongle.

i will add that i recently installed Windows 7 and SB and i did not see a message like that.

if i were you i would not let Windows scan the dongle. by scanning i assume it wants to check for and fix any errors it might find.

Thanks Kramer.The guys on the SteelBeasts forum said not to allow Win 7 to fix it either.
I am sure that when my last CM stick failed I had mistakenly asked Vista to 'fix' it.May have been a coincidence but I won't take that chance again.

I think you can safely let Windows "check" it, but if it asks to "fix" something I'd say no. I've had a couple of similar cases with other USB sticks where Win7 just wants to check and then reports that everything is actually quite okay. My guess is that it just habitually scans every new drive that gets added to the computer and then sets a registry bit that the drive is known and has been found fault free (and that it will ask you again whenever you plug it in until you finally agree to the scan). Just remember to not select "automatic repairs".

CodeMeter registers as a mass storage device so that it can use the standard driver for USB drives that is part of Windows (or other supported operating systems). That way you need not trust the vendor or the manufacturer of the stick that their driver does something kooky on your system, or that there is a driver conflicting with some other software. The rest is being handled by the CM runtime software which can be restricted in its access privileges sufficiently to satisfy even mildly paranoid users (those that are still able to trust the operating system as such).