"Failed to set data for..." error on Windows shutdown

[Polwhele]

When RegDefend (v2.001) is running, Bayden Slickrun gives the error message "Failed to set data for Slickrun" when Windows is shutdown/rebooted. Shutdown then halts with "This program is not responding" error.

I guess Slickrun wants to write to disk/update a registry entry, but have no clue what is the specific problem. RegDefend is not logging any related activity that I can see.

Any suggestions about what rule might be creating this issue, or how to investigate it further? I will also post a query to Slickrun to ask what it's doing on shutdown.

BTW I highly recommend Slickrun (http://www.bayden.com/SlickRun/). Quote: "SlickRun is a free floating command line utility for Windows. SlickRun gives you almost instant access to any program or website. SlickRun allows you to create command aliases..."

TIA

Polwhele

[tonyjl]

Hi Polwhele.

Have you tried disabling RD before shutting down?,just to make sure it is RD causing the prob and not something else. If RD isn't logging anything,maybe it aint blocking anything too log.

If it is RD,try downloading RegMon from sysinternals http://www.sysinternals.com/Utilities/Regmon.html

Disable RD,launch RegMon and set it to include Bayden Slickrun but ignore everything else,and then shutdown Bayden Slickrun,RegMon will log all keys/values accessed by Bayden Slickrun,then it's just a case of matching RegMon's logs with RD lists.

Hope that helps :)

[Polwhele]

Thanks vey much tonjl, that's very helpful.

I've tested to my own satisfaction that if RD is not running, the issue with Slickrun does not occur.

Hadn't thought about using RegMon though - I'll tackle that tomorrow.

Cheers,

Polwhele

[nick s]

Hi Polwhele,

At shutdown, it looks like sr.exe (SlickRun) sets an autostart run value for itself under this key:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

Unfortunately, the RegDefend GUI shuts down before SlickRun does. Since RegDefend's default action for that key is "Ask User", it effectively blocks sr.exe from setting its value, which then results in the "Failed to set data..." error. An application rule like this for sr.exe should get rid of that error...

Nick

[Polwhele]

Thanks Nick, the specific guidance is very helpful as I'm new to RD & haven't fully understood the rules system yet.

P

[Polwhele]

Yes that's cured it!

Thanks to you & tonyjl for great support.

P