Registry Handle Leaks on shutdown.

[mnorman]

I was doing fine with SAS free and was ready to purchase the paid addition when I downloaded the lasted build 4.50.1002 and now on every SHUTDOWN I get the following in the Event Log, Event ID 1530 with the following details:

2 user registry handles leaked from \Registry\User\S-1-5-21-2987587682-1074968332-1067063631-1001:

Process 2012 (\Device\HarddiskVolume3\Program Files\SUPERAntiSpyware\SASCore64.exe) has opened key \REGISTRY\USER\S-1-5-21-2987587682-1074968332-1067063631-1001\Software\SUPERAntiSpyware.com\SUPERAntiSpyware\SABUpdate

Process 2012 (\Device\HarddiskVolume3\Program Files\SUPERAntiSpyware\SASCore64.exe) has opened key \REGISTRY\USER\S-1-5-21-2987587682-1074968332-1067063631-1001\Software\SUPERAntiSpyware.com\SUPERAntiSpyware\SABUpdate

There's a similar thread to this dated 29 March, but no reply from anyone at SAS. I've also send an email to tech support. As I said, I have the free edition installed, no ad blocker. I'm running NOD32 AV and MS Windows Defender. Again, registry leaks started with latest build. Apparently deleting the registry keys does not good. The program simple recreates them when its run.

Thanks.

[SUPERAntiSpy]

I was doing fine with SAS free and was ready to purchase the paid addition when I downloaded the lasted build 4.50.1002 and now on every SHUTDOWN I get the following in the Event Log, Event ID 1530 with the following details:

2 user registry handles leaked from \Registry\User\S-1-5-21-2987587682-1074968332-1067063631-1001:

Process 2012 (\Device\HarddiskVolume3\Program Files\SUPERAntiSpyware\SASCore64.exe) has opened key \REGISTRY\USER\S-1-5-21-2987587682-1074968332-1067063631-1001\Software\SUPERAntiSpyware.com\SUPERAntiSpyware\SABUpdate

Process 2012 (\Device\HarddiskVolume3\Program Files\SUPERAntiSpyware\SASCore64.exe) has opened key \REGISTRY\USER\S-1-5-21-2987587682-1074968332-1067063631-1001\Software\SUPERAntiSpyware.com\SUPERAntiSpyware\SABUpdate

There's a similar thread to this dated 29 March, but no reply from anyone at SAS. I've also send an email to tech support. As I said, I have the free edition installed, no ad blocker. I'm running NOD32 AV and MS Windows Defender. Again, registry leaks started with latest build. Apparently deleting the registry keys does not good. The program simple recreates them when its run.

Thanks.

We'll take a look at this today - there is no harm to your system here.

[DooGie]

There's a similar thread to this dated 29 March, but no reply from anyone at SAS. I've also send an email to tech support. As I said, I have the free edition installed, no ad blocker. I'm running NOD32 AV and MS Windows Defender. Again, registry leaks started with latest build. Apparently deleting the registry keys does not good. The program simple recreates them when its run.

Thanks.

Yes the registry keys are recreated but only after update is run. Even if no update is available the registry keys re-appear.

If SAS is running but an update is not attempted the registry keys aren't recreated.

Still as Nick says it causes no harm and I reckon that the majority of users never check the event log anyway so would never know.

[mnorman]

Yes the registry keys are recreated but only after update is run. Even if no update is available the registry keys re-appear.

If SAS is running but an update is not attempted the registry keys aren't recreated.

Still as Nick says it causes no harm and I reckon that the majority of users never check the event log anyway so would never know.

Thanks very much. Appreciate the reply. FYI for the list: SAS tech support also says to ignore them. BTW, it's actually a good idea to check the Event Log once a week or so, particularly on a new OS like WIN7/64. Mine's OEM on a Dell 980 Optiplex, heavily tested hardware, and right from the beginning I've had to make a number of fixes -- memory handling, networking etc. All OS problems.

[SAS Customer Service]

Thanks very much. Appreciate the reply. FYI for the list: SAS tech support also says to ignore them. BTW, it's actually a good idea to check the Event Log once a week or so, particularly on a new OS like WIN7/64. Mine's OEM on a Dell 980 Optiplex, heavily tested hardware, and right from the beginning I've had to make a number of fixes -- memory handling, networking etc. All OS problems.

According to our developers; those handles do not effect the program or windows in a negative way and they are looking at fixes.