The problem with "QSettings: RegEnumValue failed" is not fonts

[Jestar]

@glosfor

If you are feeling brave, you can attempt a test. Note that this test is ONLY useful if you have run “Scrivener.exe --log” and seen repeated “RegEnumValue failed” errors getting logged. Do NOT attempt this test for any other Scrivener problem, as there is a risk that this will cause problems with products other than Scrivener.

It should probably go without saying, but I’m going to say it anyway: When making changes to your system that are proposed by anonymous guys on the internet, use at your own risk.

I was feeling brave and taking all due precautions.

@glosfor

1. If you don’t already know, figure out whether you are running 32bit or 64bit Windows.
2. Launch RegEdit (if you don’t already know how, this test may not be something you should try).
   3a) If you are running 64bit Windows, look for HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID
   3b) If you are running 32bit Windows, look for HKEY_CURRENT_USER\Software\Classes\CLSID
3. Make ABSOLUTELY CERTAIN you are looking at “HKEY_CURRENT_USER”, not “HKEY_LOCAL_MACHINE”. Editing HKEY_LOCAL_MACHINE (or some other key that is “kinda like” what I list here) would be VERY, VERY BAD (like “trash your computer” bad). If you are at all unsure (or cannot find the EXACT key described), do not proceed.
4. Use Edit/Rename to rename the CLSID key to ScrivenerTest.
5. Try to launch Scrivener.
6. Whether the launch succeeds or fails, immediately return to RegEdit and rename the ScrivenerTest key back to CLSID before doing anything else. Be careful you don’t add a space after CLSID (easy to do if using copy/paste).

This is definitely where the issue lies. I followed your instructions here except I renamed my CLSID key to “CLSID-old”, closed regedit and started Scrivener with the log function. Scrivener launched properly. I closed Scrivener and reopened regedit to find I had a new CLSID key with the Scrivener specific key in it. See screen shots. Process ID name of the Scrivener key is: Rnvrcs and appears to have the same data.

@glosfor

Let me emphasize this: Even though this might fix your Scrivener problem, do NOT leave this key renamed. There’s no way to know what all is using that key. But whoever it is, they will be unhappy if it is missing, and there’s no telling what bad things might happen as a result.

The other CLSID keys were easy to figure out and did not seem to bother the operation of the PC or software.
FWIW: msdn.microsoft.com/en-us/librar … 53(v=vs.85.aspx

@glosfor

If you attempt this test, here are the things to report:

1. Did you run the “Scrivener --log” test and see the “RegEnumValue failed” message?
2. Did your computer have the exact CLSID key described in steps 3a/b?
3. Did Scrivener successfully launch after you renamed the key?
4. What version of Windows (7? 10?) are you running? 64bit or 32bit?
5. Are you (like me) running any of the Tortoise* tools for software version control (TortoiseSvn, TortoiseCvs, TortoiseGit, etc)?

1. Yes, no on the error message.
2. Yes for 3A.
3. Yes.
4. Windows 7 64-bit SP1 (fully patched).
5. No, not on this machine or on a machine with Scrivener installed.

@glosfor

What this will tell us:

The problem here probably isn’t due to any of the programs that use that registry key (although it might be, which is why I’m asking about Tortoise). Collecting a list of installed programs we have in common might be interesting.

But mostly what I expect to learn is that everyone who is getting this QSettings message has this key. The key is not always created (or needed), which is why creating a new profile works for some people: The new profile doesn’t have this key.

However if (as I expect) renaming this key solves the problem for people, then L&L will have an easy fix they can apply to their software (fixing their copy of the QT toolkit as I described at the top of this thread). If the L&L people are uncomfortable making the change, I can post a corrected copy of the childKeysOrGroups routine (but you’ll still have to rebuild the QT library yourselves).

Unfortunately I can no longer run this test myself, since Scrivener is no longer failing to launch on my machine. Darn the luck…

I can make Scrivener break on that user by swapping the CLSID key names. It might be interesting to make a copy and then remove the other software CLSID entries to see if one of them fixes the Scrivener key; however, I think that it won’t make much of a difference. The only two keys I have found between the two users that are common are both for Grammarly:

HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID{2AD206F1-152C-4F9D-A24E-6F93FE7A4AFC}

• and -
  HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID{4BE56754-B616-4998-B825-D16983AEE1B2}

In my working Scrivener user, those two keys are present. In my previously non-functional Scrivener user they were there, but not in the new functional version of CLSID. Grammarly does work properly for the user without those two keys.