KNOWN ISSUE: Get Registry Key Value action does not read lines of REG_MULTI_SZ after a line containing an empty string
search cancel

KNOWN ISSUE: Get Registry Key Value action does not read lines of REG_MULTI_SZ after a line containing an empty string

book

Article ID: 176529

calendar_today

Updated On:

Products

Symantec Products

Issue/Introduction

Steps to duplicate:
  1. Create a new .WSE.
  2. Add a Edit Registry key action that creates a multi-string registry key with the value:
        Line1
        Line2

        Line3
  3. Add a Get Registry Key Value action that reads the registry key created above.
  4. Display a message with the registry key value.

The message will only display:
Line1
Line2

Cause

According to Microsoft, multi-string registry keys should have one null to separate each string in the array, and two nulls to indicate the end of the key. Based off of this, Line2 should be the end of the registry key. If you open the key in Regedit on Windows XP*, you will receive a message indicating a multi-string registry key cannot contain blank lines and the blank line will be removed.

However, there are still some Microsoft keys that can contain a blank line. One of these is the PendingFileRenameOperations key which is used to update files that are in-use during installations. To delete a file that is in use, a blank line should be placed in this key.

Resolution

Workaround: There is no known workaround at this time.

Applies To
Wise Installation Studio/Express 7.0
Wise Package Studio 7.x
WiseScript Package Editor