Summary
This article documents the behavior witnessed in bug FNMS-29295 where a beacon will revert to the default install directory during a self upgradeSymptoms
Once a beacon gets / performs a self upgrade because a new version was deployed centrally (batch server) it removes the value inHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Beacon\CurrentVersion\BaseDirectory
This causes significant issues e.g. the beacon loads an outdated configuration looking into an outdated path, if existing at all. What can be done to prevent the change to the BaseDirectory value?
Resolution
This behavior is caused by a known issue. When an inventory beacon perform a silent upgrade it will automatically revert to the default install directory. The only current workaround for this issue is to manually modify the changed registry keys following the install. This issue can be tracked through reference FNMS-29295Was this helpful?
Related Articles
Manually upgrading a beacon with the full installer UI removes registry keys containing replication configuration settings 4Number of Views Backward Compatibility for Toolkit Upgrade and Keys (vendor_keys, TRL,ENCRYPTION_KEYS) Change 21Number of Views NT User Permissions for Installed Directories, Files, and Registry Keys 4Number of Views Correct Method for Specifying Registry Keys 3Number of Views Custom registry keys for Snow Windows Inventory Agents 144Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago