Skip to main content

Disable autorun using gpedit.msc

To disable Autorun feature of Windows, follow this instructions:
  • - From your desktop, click Start.
  • - Click Run…
  • - Type gpedit.msc in the drop down box.
  • - Hit Enter key from your keyboard.
  • - Group Policy will appear after pressing the Enter key.
  • - Under Computer Configuration double click Administrative Template to collapse the sub menus.
  • - Click the System folder.
  • - From the right side of the window, double click the Turn-Off Autoplay setting.
  • - Click the Enabled radio button to enable the settings.
Labels:

Popular posts from this blog

The security log on this system is full. Only administrators can log on to fix the problem.

The security log on this system is full. Only administrators can log on to fix the problem. To resolve this issue, use an account that is a member of the Administrators group to log on to the computer. Then, follow these steps to specify that Security log events can be overwritten: 1. Click Start, point to All Programs, point to Administrative Tools, and then click Event Viewer. 2. Right-click Security, and then click Properties. 3. In the Log Size area of the Security Properties window, click the Overwrite events as needed option under When maximum log size is reached. 4. Click OK. 5. Close Event Viewer.
11 comments
Read more

CWBLM0011 - An Internal License Management Error Occurred.

CWBLM0011 - An Internal License Management Error Occurred. RESA II started recieving error messages when users would sign on with client access express running on Windows 2000, the first client would connect but the second would get a license code error that said internal licensing error, here is a description from IBM's website, "Windows NT/2000 Restricted Users (User Group) attempting to start a 5250 terminal emulation session running Client Access Express (5769XE1) V5R1M0 receive a CWBLM0011 error message. This error does not occur when logged on to the PC as the Windows Administrator. The error appears more frequently when the users attempt to start multiple Client Access sessions." It appears to happen because the user doesn't have permissions to update some registry keys that client access likes to update occasionally, so this error message can happen at any time and doesn't appear to have any rhyme or reason. In RESA II's case, Tim believed it was ca...
6 comments
Read more