hey up folk, how is ? tn here with a slightly odd problem. I am just messing about with adding some REG edits to my Win 8.1 image. I am using DISM. on a Win 8.1 machine. At the mo I have 17 added,tested and working really nicely but one is eluding me and I can not understand why. The edit I have works fine on Win 7 but does not work on Win 8.1 Open .nfo files with Notepad. Here is my edit. I must be missing summet for why this REG Edit does not work. Can anybody help me out here and see what I am doing wrong. Once the Win 8.1 is installed and I manually assign .nfo to open with Notepad, it works fine.
I have no use for notepad + +. All I want is for my machine to recognise .nfo files and open them with Notepad. Often downloaded stuff comes with info on a .nfo file. I can and will do it manually if needed but I can not understand why this REG edit does not work on Win 8.1
I found this one here someplace and have been using it OK with Windows 8.1: [HKEY_CLASSES_ROOT\*\shell\Open with Notepad] [HKEY_CLASSES_ROOT\*\shell\Open with Notepad\command] @="notepad.exe %1"
I have saved this info and will be testing it out shortly. I am a bit confused though. What has this info got to do with .nfo files ? Or do I have to add it to my existing bit of code ?
Win8.x likes to use some sort of roaming file associations. If you change the system's associations in the win7 spot it won't do anything. You have to also change the roaming association. The branch will look similar but it will have 'roaming' somewhere in the key. That's all I remember. Keep searching the registry in regedit.exe for the extension (.nfo in your case) I found this out the hard way when I wanted to un-assign wim files to 7z.
I have just opened registry and searched for .nfo I have found 8 instances where .nfo appears within the registry and exported these out into .reg files. I am just about to do another test install of Win 8.1 onto my test rig with some reg edits integrated but .nfo is NOT one of them. Once it is installed I will open up these exported reg files I just made and compare them to a fresh machnes registry where .nfo files are NOT associated to the notepad. and note down any differences. Then try to complie a new reg file where I can make .nfo open with notepad. Seems like a good plan, whether it's the right way to go about this I am not sure. We'll see...
Eh... just keep in mind that it might not add the .nfo to certain registry keys until it's modified. If you really want to be certain you can try installing/running damn nfo viewer until it makes the association for you, then you can easily find the key.
Summet interesting. After the fresh install. the registry can only find two instances of .nfo I have manually associated and rebooted the system. Just this very second I am gunna search the registry again. Interesting.. After manually associating .nfo files there are now four instances in the registry. I am just gunna copy them over to my main machine to compare with my first set of files. I have a feeling cause I do remember running the original reg edit on this machine I am getting false reg instances that are actually doing nothing.. be right back..
I think explorer might need to be taskkilled and restarted when you change the keys, or reboot. I seem to remember doing that, but I opted for the reboot since you have to admin the taskkill and explorer doesn't normally run as admin.
TUT. TUT.TUT Just as it was getting good, company came a knocking at my door. hey ho.. So let me go over what I have found. I did a new install of Win 8.1. There was no association to .nfo files and when I did a search in the registry I found only two instances of .nfo. I manually added an association with .nfo files to open with Notepad. I rebooted the PC. Sure enough once the PC started up my home made .nfo file had the Notepad icon attached and Notepad opened when I double clicked on it. I then did a new search in the registry for .nfo and found four instances. Notice the registry address, if that's the right terminology, it is totally different to the one in Win 7 and the original reg edit file I started with. What I will test now is to save these reg files. turn off he Notepad association then run the reg files and see what happens. Hope this all makes sense.
No that does not work.. But..reading it carefully there is what you mentioned, ROAMING... off to think for a mo..
Finding and running a reg file takes just as much time as right-clicking on the .nfo file, selecting 'open with', and selecting notepad from the list (making sure the 'Use this application for all .nfo files' is checked). If you look at the references to how the files are opened above, you will see . The issue with that is the user ID, the S-1-5-21-550689642-3005006457-2284042826-1001, is a unique identifier for that user. This means that if you plan to use the registry file again on a different install, or on a different computer, the identifier location will be different. There is another way to do it besides using a reg file (and without using a third party file) but the method escapes me at the moment.
I agree with burfadel. Much easier to just "open with". Personally I still use "DAMN_NFO_Viewer_v2.10.0031.RC3_Setup" which was release in 2003 I think. Works fine...
Does there exist a HKEY_USERS\.DEFAULT in Win 8.1? You might have some success with that user ID as it is acting as registry template for all new accounts (at least local ones). Try to replace that cryptic account ID with the .DEFAULT one. Of course it doesn't affect already existing accs.
In this case, you have to import the reg file, what will kill the NFO association to MSInfo (msinfo32.exe) application 1st.
Make it like .txt file i always used this since XP Code: ; Associate Text Files [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.sif] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.sif\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.diz] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.diz\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.lst] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.lst\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.nfo] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.nfo\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.ssa] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.ssa\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.srt] @="txtfile" "PerceivedType"="text" "Content Type"="text/plain" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.srt\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cfg] @="inifile" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cfg\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.conf] @="inifile" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.conf\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}"