General discussion


Software Restrictions broken

By dmead74 ·
Evidentally Windows XP's Software Restriction policy implementation is broken. Some of my users have discovered that by crashing Explorer they can remove the restrictions completely. That's right, they can run anything from anywhere. I run a high school network, so we have some pretty tight restrictions normally.

All that needs be done is to try to read a damaged floppy disk. While it's struggling, close My Computer, and boom. Explorer crashes, restarts, and restrictions are gone. I haven't been able to find any reference to this problem anywhere.

Is there a fix for this? Does MS know about it? (I've tried to tell them, but I'm not paying $99 for the priviledge of a 'problem report') Is there a decent way of reporting bugs to MS? Is my only option crippling my workstations (disabling removable media, or preventing Explorer restarting after crash)?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by p.j.hutchison In reply to Software Restrictions bro ...

Windows is not the best tool to repair broken disks. Try booting into DOS with a dos boot disk and repair it that way, otherwise repair it with a Disk utility and NOT Windows.

There is no fix as such. You need to use the correct tools for this.

Collapse -

by dmead74 In reply to

Sorry p.j. but I don't think you read my post properly. I'm not asking about fixing disks, I'm asking how to fix the exploit for the software restriction policies.

Collapse -

by razz2 In reply to Software Restrictions bro ...

I understand what you are saying and the issue is because when
Windows Explorer (desktop) restarts as describbed it does not
load the same as on boot. You will notice many times that not all
the startup apps come back either. I would say that a failed CD
would not cause the source of the problem and not crash
explorer as the floppy does. Ban floppies and use Group Policy
to disable floppies.

They may still be able to do a Task List and kill and restart
explorer so I use GPO's to prevent taskList access too.

Good Luck,


Collapse -

by dmead74 In reply to

Yeah, that would work for the time being. But the users do have legitimate use for having access to A: and it would be better not to take it away arbitrarily. It would be a temporary solution at best as I'm sure they'll find another way to crash explorer.

Collapse -

by ReWrite In reply to Software Restrictions bro ...

What happens if you turn off the automatic reboot on system failure. Then the system would not automatically reboot and force the user to manually turn the machine off and back on.

To turn off automatic reboot follow these steps:

Open System Properties via Start > Control Panel > Performance and Maintenance > System.

Select the Advanced tab and then click Settings in the Startup and Recovery section.

In System Failure section, clear the checkbox next to Automatically Restart.

Click OK and OK to exit.

Automatic reboot is turned on by default in WinXP.



Collapse -

by dmead74 In reply to

This looks like it'll be my best option. I'll have to create a custom administrative template to do this through a GPO though. The registry key is easily located. It may cause some inconvience but it's about as good as I'll get by the looks of things.

Collapse -

by dmead74 In reply to Software Restrictions bro ...

This question was closed by the author

Related Discussions

Related Forums