Place a DWORD invers le Registre avec a valeur beyond accepted limit

[ForumBot]

Il y a an problème we encounter where DWORD valeurs in `HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall` avec data which breaches the upper limit for a DWORD valeur (that is, anything over DEC 4294967295) will cause our logiciel to fail when parsing the Registry parce que valeurs this high devrait être stored as QWORDs, not DWORDs. Accordingly I'm writing some PowerShell to detect the presence duse invalid valeurs and highlight them so they can be corrigé.

It n'est pas clear where these broken valeurs are coming from, but they come up often enough for it to be a problème.

What I need maintenant is a way to place these invalid valeurs invers le Registry dans le first place such that Je peux verify my checks are en fait fonctionnel. In essence, J'ai besoin de *break* my Registry afin de *fix* it.

Ici is what J'ai tried:

- PowerShell: "Value was either too large or
too small for a UInt32."

- Regedit: Physically impossible to enter too many digits

- Export/Edit/Implant .REG fichier: Data are imported but ne pas appear in Registry

C'est good that these tools have protection built-in, but clearly there's *some* way to do it otherwise we ne serait pas have to worry about solving this problème. Can anyone propose a way to get this invalid data invers le Registry?

[ForumBot]

Velvet's answer is correct. I gave this to a tame developer who turned it into a command-line app which places the Registry data into a predefined location and it does indeed break the Registry.

I could post the application ici, but J'ai découvert après experimenting that J'étais able to export the broken information as a .REG fichier and re-import it to break the Registry successfully, making this unnecessary.

Ici is the REG fichier's contents:

```
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Test123]
"DisplayName"="Invalid Software"
"Version"=hex(4):bf,02,00,00,01,00,00,00

```

The reason I said in OP that this ne pouvait pas be done was parce que J'étais making a broken REG fichier improperly. C'est un proper improper, unbroken broken REG fichier which will fail the task successfully.