Inno Setup - Registry Key Values are not visible after install in HKLM?

22 views
Skip to first unread message

Andrew Truckle

unread,
Nov 9, 2021, 12:56:03 PM11/9/21
to innosetup
I have some entries like this in my installer:

    ; Localized registry entries
    #include AddBackslash(SourcePath) + ".\l.afk\RegistryEntriesEnglish.txt"

Infact, I have 48 of them. There is an example file:

```
; English registery entries
[Registry]
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: ReportTitle; ValueData: Sound Rota Schedule; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: DateHeading; ValueData: <Date; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Sound1Heading; ValueData: <Sound 1; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Sound2Heading; ValueData: <Sound 2; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Sound3Heading; ValueData: <Sound 3; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Sound4Heading; ValueData: <Sound 4; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: PlatformHeading; ValueData: <Platform; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: PlatformMikeHeading; ValueData: <Platform Mic; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike1Heading; ValueData: <Mic 1; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike2Heading; ValueData: <Mic 2; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike3Heading; ValueData: <Mic 3; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike4Heading; ValueData: <Mic 4; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike5Heading; ValueData: <Mic 5; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Mike6Heading; ValueData: <Mic 6; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Attend1Heading; ValueData: <Attendant 1; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Attend2Heading; ValueData: <Attendant 2; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Attend3Heading; ValueData: <Attendant 3; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English
Root: HKLM; Subkey: Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings; ValueType: string; ValueName: Attend4Heading; ValueData: <Attendant 4; Flags: uninsdeletekey createvalueifdoesntexist; Languages: English

```
If I check the installer log:

```
2021-11-09 17:47:58.489   -- Registry entry --
2021-11-09 17:47:58.489   Key: HKEY_LOCAL_MACHINE\Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings
2021-11-09 17:47:58.489   Value name: ReportTitle
2021-11-09 17:47:58.489   Creating or opening the key.
2021-11-09 17:47:58.490   Creating or setting the value.
2021-11-09 17:47:58.490   Successfully created or set the value.
2021-11-09 17:47:58.490   -- Registry entry --
2021-11-09 17:47:58.490   Key: HKEY_LOCAL_MACHINE\Software\MeetSchedAssist\Meeting Schedule Assistant\eng\Headings
2021-11-09 17:47:58.490   Value name: DateHeading
2021-11-09 17:47:58.490   Creating or opening the key.
2021-11-09 17:47:58.491   Creating or setting the value.
2021-11-09 17:47:58.491   Successfully created or set the value.
```
It appears they are being created. And teh installer is elevated.

Yet when I run Reg Edit they are not visible?

    HKLM\Software\MeetSchedAssist\Meeting Schedule Assistant\Options

Andrew Truckle

unread,
Nov 9, 2021, 12:57:13 PM11/9/21
to innosetup
I was a donut. They were saved to WO6432Node ... :)
Reply all
Reply to author
Forward
0 new messages