Windows 10: A REGISTRY mystery - reg file doesn't import properly

I have used reg, Kyhi has fixed, and all entries imported just fine. Try to use bat instead.

 

Attachment 121731 here is your corrected reg file..

I believe he had WORDWRAP enabled in notepad

or now after reading the ( last page )which I failed to read..
It may of been the program he used did not like spaces / or semi-colons

Just a little FYI:
Qoutes " " are wrapped around commands that have spaces...
Otherwise the command breaks at the space..

Example
Cmd C:\New Folder > is seen as C:\New
Cmd "C:\New Folder" > is seen a C:\New Folder

Thus the give away hint in the first post = quotes all over the place
Thus being read as several single lines of unknown code
rather than a single line of code

 

@Kyhi
thx, but if I export the key with regedit, delete the key in the registry, then clk the .reg file and import it, I have changed nothing in the .reg file that regedit (a MS program) created. Based on what I saw in notepad previously, I figured there was a problem with those lines, but MS created them, so who am I to question MS...........
So this obviously is a newly created bug from GOD MS, since sometime in the past it worked fine.

 

it's fixed now in the reg file...
Enjoy!!

 

well, this issue isn't resolved and the link to the "fixed" file doesn't work.
The registry names that do not import contain CR CR LF at the end of each line in the value
The value in the program that created the entry looks like this

G1 Z5 ; lower bed
G1 X50 Y260 f5000 ; move to back left
G28 Z0 ; test Z0

That is one value for a script name with CRs & LFs

The reg file contains this:




So the 0d 00 0d 00 0a 00 is terminating the " and since that makes it invalid the entry is dropped on import.
So how does the program create it in the first place?
and just eliminating those CR LF is not going to recreate what is in the program.

 

Just to commiserate a bit, I was 'taught' early in my computing days to never use a word processor program such as Word, Wordpad, WordPerfect, WordPro, etc., to edit such files as the Registry or for programming such as .exe files as there's always hidden coding in the documents but to always use a Text Editor such as Notepad. I haven't tried yet with Notepad++.

 

I think the question is, what is software do you have registered to open reg?

I have exported a long line, it exported cut by slashes, but it imports OK.
In wordpad, it has added spaces, but even altered, it imports just fine.
So it is most likely you have something messed up with reg classes.

 

@TairikuOkami thanks but you are not seeing the problem. What you have posted has nothing to do with the problem. Review my last post again. The program that created the registry entries in the first place is Repetier Host a 3D printer program. It recorded multiple printer commands separated by CR/CR/LF as a single value in the registry. Regedit appears to export them correctly as seen in the Ultraedit snapshot, but upon import is relying on a CR or LF or both to terminate the " thereby seeing an invalid entry and dropping it (without any warning by the way). The CR and LF in those entries are part of the entry (as shown in my post) and should be imported intact as one value. Regedit should rely on the next " to terminate it, but God knows what other issues that would create when the other " was actually missing.
So how did Repetier manage to create these entries? And is there any possibility I can import them - It isn't going to happen with Regedit unless MS changes the way they handle CR/LF. If I change the data type then Repetier probably won't be able to read it.

 

Well, I long for the old INI files. They were easy to fix and modify. But the registry is "suppose" to be just one big INI file. Somehow, Repetier Host is manipulating the registry and making it work for them. BUT regedit can't handle its own creation.
I don't know if what Repetier is doing is defined by MS as being non-conforming. If I knew that I would go back to Repetier to fix their product. But one of them is not right because a basic function (export/import) does not work. I venture to say that a registry backup and restore would not work either, but it may be implemented different than an export/import.