I am working on a client's computer. Between the old HDD and her grandchildren fidgeting, her old user account was badly corrupted. The old IDE was over its lifespan. It had no pictures or documents on it. The computer could have easily supported 64-bit Windows, but someone installed 32-bit instead when I was out of town for an extended period. I chose to do a fresh install of Microsoft Windows 7 Home Premium 64-bit on a brand new HDD. I completely separated the Administrator account from the standard ones. Next I added a legal disclaimer to her pre-logon screen. Run was successfully disabled after changing the hive in the Admin account. Then I tried to disable command prompt. I added 'DWORD (32-bit) value' 'DisableCMD' 2 under 'HCU/Software/Microsoft/Windows/CurrentVersion/Policies/System.' It did not work at all. Normally it would. I looked and looked to no avail. Changing cmd.exe name or simply disabling their ability to use it from security can be easily bypassed. This is so irritating. What do you believe could be causing this problem?
post #1 of 5
11/14/12 at 9:56am