Is there a way to make icons apear manualy?
I saw the icons in the files, so...
Your script needs updating
Code::pow2 cd /d %~dp0 REGEDIT /s Files\Reg\Install_Epo.reg xcopy Files\Epo C:\Windows echo Done installing. Have a ****ed day. pause exit
Should read:
Code::pow2 cd /d %~dp0 REGEDIT /s Files\Reg\Install_Epo.reg xcopy Files\Epo C:\Windows xcopy Files\Pow C:\Windows echo Done installing. Have a ****ed day. pause exit
Or you should put all the power icons into one folder.
@pbanj
You made a small mistake in Hidden_Files.vbs. If the user click "Hidden Files" in the context menu, it doesn't show SuperHidden files as the Reg variable is always set to 0
Code:[---] If Check = 2 Then Command1.RegWrite Hidden, 1, "REG_DWORD" Command1.RegWrite SSHidden, [B][COLOR="Red"][SIZE="5"]0[/SIZE][/COLOR][/B], "REG_DWORD" [B][COLOR="Green"][SIZE="5"]<-- Replace 0 by a 1[/SIZE][/COLOR][/B] Else Command1.RegWrite Hidden, 2, "REG_DWORD" Command1.RegWrite SSHidden, [B][COLOR="Red"][SIZE="5"]0[/SIZE][/COLOR][/B], "REG_DWORD" End If [---]
However, nice work
You should add "shut down" AND "shut down (hybrid)", like AskVG's version has. Two different ways to shut down w8/8.1 you know
Hi,
I have a Surface RT winth 8.1 and running as administrator your Script I'm having "You fail RTFM" error. Any idea why? And how to solve it?
Thanks,
Jesus.
i hate to say it but read the manual... there is a readme in there for a reason.
This will install a menu to your context(right click) menu. items include regedit, open cmd here(normal and admin) show/hide known file types, show/hide hidden files/folders, and open admin powershell here.
steps
1. Run Tools.bat as admin
2. Follow what it says
3. If icons dont show up reboot or restart explorer
Changelog
v0.2 - added open powershell as admin here, fixed open cmd as admin here, no longer need ele.exe and the e.cmd file
v0.3 - able to remove the restart explorer.bat file thanks to coldbloc
v0.4 - added power menu. normal has lock, logoff, restart, restart with boot options, and shut down. the second has all of the first but sleep, hibernate, and switch user.
v0.5 - fixed an issue in the hidden files vbs(thanks LEDelete for pointing it out), fixed missing icon folder copy command in install script (thanks trm96 for pointing that out) should fix icons not showing up
-_- that error only comes up when you don't follow the readme............. By you getting that error you are not following the first step. The only way that message shows up is if it fails the check to see if its run as admin.Hi,
I have done... Here all that my readme.txt have:
What should I do?
Thanks!
You know dude, I appreciate the ability of noobs to screw things up more than most people on this forum, but have you considered the possibility that, when somebody explicitly tells you that they are running the script as Admin they are, in fact, running the script as Admin?
Your attitude is remarkably and unwarrantedly arrogant. In this particular case, the problem was easy to find: you use APIs in your VBScripts that Windows RT disallows unless the scripts are signed (or the OS is jailbroken). However, you never mention that your tools won't work on RT unless it's jailbroken, and since it's "just" scripts, many people will (more-or-less accurately) assume that the tools should be usable on Windows RT. However, rather than providing useful error messages when a problem occurs, you assume any failure of your perfect script is obviously just due to user error!
Oh, and as a side note: you can have a script automatically request elevated privileges. Rather than giving a snarky error message, and telling people to read the help files, why not just automatically request the required privileges?
. Not "Hmm, that error message is supposed to mean something in the check for Admin failed" or "that's weird; if you run it as Admin you shouldn't ever see that error". Nope, just "there's only one thing that could cause that (because the code can't possibly have bugs, right?), so it's your fault". You claim you never said it was compatible with RT (this is true, and indeed your earlier versions that had executables in them wouldn't have been without additional hacks) but you never said what it *was* compatible with, nor did you say "well, I never tested it on RT, so maybe that's why you're getting the error?" or something similar.that error only comes up when you don't follow the readme............. By you getting that error you are not following the first step
A security identifier (SID) is a unique value of variable length that is used to identify a security principal or security group in Windows operating systems. Well-known SIDs are a group of SIDs that identify generic users or generic groups. Their values remain constant across all operating systems.
SID: S-1-5-32-544
Name: Administrators
Description: A built-in group. After the initial installation of the operating system, the only member of the group is the Administrator account. When a computer joins a domain, the Domain Admins group is added to the Administrators group. When a server becomes a domain controller, the Enterprise Admins group also is added to the Administrators group.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*\shell\runas]
@="Take Ownership"
"NoWorkingDirectory"=""
[HKEY_CLASSES_ROOT\*\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant *S-1-5-32-544:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant *S-1-5-32-544:F"
[HKEY_CLASSES_ROOT\Directory\shell\runas]
@="Take Ownership"
"NoWorkingDirectory"=""
[HKEY_CLASSES_ROOT\Directory\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant *S-1-5-32-544:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant *S-1-5-32-544:F /t"
. Not "Hmm, that error message is supposed to mean something in the check for Admin failed" or "that's weird; if you run it as Admin you shouldn't ever see that error". Nope, just "there's only one thing that could cause that (because the code can't possibly have bugs, right?), so it's your fault". You claim you never said it was compatible with RT (this is true, and indeed your earlier versions that had executables in them wouldn't have been without additional hacks) but you never said what it *was* compatible with, nor did you say "well, I never tested it on RT, so maybe that's why you're getting the error?" or something similar.that error only comes up when you don't follow the readme............. By you getting that error you are not following the first step
[---]
If Check = 2 Then
Command1.RegWrite Hidden, 1, "REG_DWORD"
Command1.RegWrite SSHidden, [B][COLOR="Red"][SIZE="5"]0[/SIZE][/COLOR][/B], "REG_DWORD" [B][COLOR="Green"][SIZE="5"]<-- Replace 0 by a 1[/SIZE][/COLOR][/B]
Else
Command1.RegWrite Hidden, 2, "REG_DWORD"
Command1.RegWrite SSHidden, [B][COLOR="Red"][SIZE="5"]0[/SIZE][/COLOR][/B], "REG_DWORD"
End If
[---]
Just installed, and I too am having trouble with icons not properly displaying. I've tried restarting explorer...no help...and rebooting PC several times, and also shutting down...waiting a bit, then restarting...same issue. See screenshot.
BTW...I'm on a new MS Surface 2 Pro...for what that's worth.
[FONT=monospace]
[/FONT][HKEY_CLASSES_ROOT\Directory\background\shell\Tools]
"MUIVerb"="Tools"
"SubCommands"="regedit.Tools;Open Admin Cmd here.Tools;Open Cmd Here.Tools;Files Extensions.Tools;Hidden Files.Tools;Restart Explorer.Tools"
"Icon"="C:\\Windows\\tools.ico"
"Position"="Top"