petrus Posted December 1, 2013 Posted December 1, 2013 (edited) Is there a way to permanently disable the following pop-up message which appears when merging .reg files? This:"Adding information can unintentionally change or delete values and cause components to stop working correctly. If you do not trust the source of this information in (path to registry file), do not add it to the registry. Are you sure you want to continue?"It's driving me nuts, and even after searching around Google for a while i couldn't figure it out. Thanks.<EDIT />And solved, just adding the /s silent switch to the registry does the trick:Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT\regfile\shell\open\command]@="regedit.exe /s \"%1\""This way registry files are merged without any confirmation pop up whatsoever! Edited December 1, 2013 by Yzöwl Two concurrent posts merged and code box added
Yzöwl Posted December 1, 2013 Posted December 1, 2013 Good luck with never accidentally invoking one!
DosProbie Posted December 1, 2013 Posted December 1, 2013 (edited) I disabled the notification pop-up for the recycle bin as well..use to drive me nuts..plus if file is deleted by mistake you can always retrieve it from the recycle bin as well (provided you have not done the empty)..DP Edited December 1, 2013 by DosProbie
CharlotteTheHarlot Posted December 1, 2013 Posted December 1, 2013 (edited) Good luck with never accidentally invoking one! Exactly. This is what is meant by working without a net. ( Image Source: here ) Just IMHO but this is an incredibly bad idea. It's bad enough that .REG files have that association in the first place ( it is much better to assign them to a text editor, not REGEDIT.EXE ), but the latest dumbing down of the Windows shell includes possible single click execution ( "OPEN" verb ) of files, or worse, no click execution thanks to touchpads opening the object when the pointer is held over it for a period of time! That last warning can be literally like a lifeboat to safety. Imagine you have a folder full of saved .REG files ( which would be really dangerous if they are complete system exports perhaps from other computers, or has deleted keys like [-HKEY ) and you are poking around that folder and the touchpad sends a complete 100 MB export ( HKLM/System included ) to REGEDIT silently. You will blow away so many system settings before it finally fails ( because it will crap out on some keys you cannot modify on a live system ). My advice is to assign .REG to an editor. For importing REG scripts I keep a shortcut icon to REGEDIT.EXE available ( Quicklaunch or Desktop ) for manually dropping .REG files on. This still provides that last warning too as long as you don't edit that shortcut and add the /s switch. If you insist on saving that microsecond of effort of clicking away that warning, then I suggest studying for the worst case scenario of how to replace a FUBAR'd registry ( you will be on a functioning live system that now has a corrupted registry on disk but you won't see the effects until the next reboot ). It is not an easy thing on NT to exchange hives, and this assumes that you managed to save good backup copies of the current working one. EDIT: before someone mentions it, in that photo it looks like the guy has a safety line attached to the tightrope dragging behind him ( still a scary photo! ). Consider that little safety line equivalent to that last REGEDIT warning prompt. Edited December 1, 2013 by CharlotteTheHarlot
MrJinje Posted December 2, 2013 Posted December 2, 2013 (edited) Nicko McBrain says: He is a big boy and understands the risk. I see no difference here than if he were to go randomly double clicking a folder full of .cmd or .vbs files which can do equal if not more damage. Anyone have the same setting for powershell. Edited December 2, 2013 by MrJinje
CharlotteTheHarlot Posted December 2, 2013 Posted December 2, 2013 Nicko McBrain says: He is a big boy and understands the risk. Kinda figured you did. I was thinking of the others not so well versed. No offense meant! Nicko always plays without a net ( Image Source: here )
petrus Posted December 2, 2013 Author Posted December 2, 2013 No worries, this is just for experimenting on a virtual machine, to figure things out, not for a deployed system.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now