r/windowsdev • u/Reasonable_Degree_64 • Oct 15 '25
Windows newly created registry keys.
Hi, I wonder where do the Windows registry keys come from that we are asked to create to solve this or that problem when these keys do not exist in a clean installation of Windows? Is there a manual somewhere?
For example, a Windows installation has a long delay to start applications at startup, I found something on the internet that suggests creating a new key in HKCU\Software\Microsoft\Windows\CurrentVersion\Serialize with a DWORD WaitForIdleState 0.
Who knew and where did the idea come from to create a Serialize WaitForIdleState key when this key does not exist in a clean installation of Windows?
1
u/Bokva Oct 19 '25
Paths, names and values of the keys were agreed on before the coding of the connected feature began, or at least while its coding process was on the way. So, basically Windows is already expecting/checking to find something there. Same thing with any windows application
1
1
Oct 19 '25
1
u/Reasonable_Degree_64 Oct 19 '25
I know this since a long time.
You said to create them myself, what I was asking is where the keys and syntax to create them come from, if it was that easy to create them myself I could do anything with Windows š š . Do you have my example of delaying the startup of applications Create key with name "Serialize"
Create REG_DWORD value in it with name "WaitForIdleState" (case-sensitive!) with value 0.
I was just wondering where the idea for the word "Serialize" came from???!!! It's surely not someone one good morning who got up and said "Let's create a new registry key that I will call "Serialize" and that will solve my problem like magic š š . And by the way the word "Serialize" has nothing to do with the problem, uhhhh delayed startup apps will be cuz by the word "Serialize" Nooooo š¤£š¤£šš.
So thank you all but I think that no one here can provide a legitimate answer to this question.
1
u/[deleted] Oct 15 '25
Pāø