How We Resolved a Genius Software Runtime Error 91 on Windows Server 2019 RDS After Storage Migration

Modern accounting and taxation software often relies on legacy runtime components, Windows compatibility settings, registry access, and application-specific initialization methods. During a server storage migration, even when all files and NTFS permissions are copied successfully, certain applications may behave differently for specific users.

This article presents a real-world technical case study involving a Windows Server 2019 Remote Desktop Services (RDS) environment where only a few users encountered Runtime Error 91 while launching Genius software after migrating data from one hard drive to another. User names, group names, and system identifiers have been changed to protect privacy.

Advertisement

Environment

  • Operating System: Windows Server 2019 Standard
  • Multi-user Remote Desktop Services (RDS)
  • Multiple concurrent accounting users
  • Legacy accounting software (Genius)
  • Data migrated from an old HDD to a new SSD
  • Migration performed using Robocopy while preserving NTFS permissions

Migration Scenario

The organization upgraded its storage by replacing an older hard drive with a faster SSD.

The migration included:

  • Complete data transfer
  • NTFS permissions
  • Ownership
  • Security descriptors
  • File attributes
  • Folder structure

Robocopy was used with security-preserving switches to ensure the new drive matched the original installation.

Initially everything appeared normal.


Problem Observed

After two to three days, a few users reported that Genius would no longer start.

Only selected users experienced the issue while most users continued working normally.

Error displayed:

 
Run-time error '91'

Object variable or With block variable not set

 

Later another affected user also reported:

 
Runtime Error 216
 

Initial Assumptions

Several possible causes were considered.

  • Incorrect NTFS permissions
  • Missing file ownership
  • Group policy restrictions
  • User profile corruption
  • Registry permissions
  • Damaged installation
  • Missing runtime components

Troubleshooting Performed

1. Verified Folder Permissions

Application folders were checked using:

 
icacls "D:\Application Folder"
 

Results confirmed:

  • Users had appropriate access
  • NTFS permissions were correct
  • Inheritance was functioning properly

No issues were identified.


2. Compared User Groups

Affected users belonged to custom departmental groups.

Working users and affected users were compared using:

 
whoami /groups
 

Both contained:

  • BUILTIN\Users
  • Remote Desktop Users
  • Authenticated Users

Only additional departmental groups differed.

Since many users in those same groups worked correctly, group membership was ruled out.


3. Tested Local Administrator Membership

An affected user was temporarily added to:

 
Administrators
 

After logging off and back in:

  • Genius still failed when launched normally.

This confirmed that simply belonging to the Administrators group was not the solution.


4. Run as Administrator Test

Next, Genius was started using:

 
Right Click
→ Run as administrator
 

The application opened successfully.

This proved:

  • Software files were intact.
  • Runtime components were loading.
  • The issue occurred only during normal application startup.

5. Investigated Windows Compatibility Settings

The executable properties were examined.

 
Properties
→ Compatibility
 

One setting immediately stood out.

 
✔ Run this program as an administrator
 

After enabling this option for the affected user:

  • Genius launched successfully.
  • Runtime Error 91 disappeared.
  • Runtime Error 216 disappeared.
  • No further application errors occurred.

Root Cause

Although all application files and permissions had been migrated successfully, Windows was launching the executable differently for certain user profiles.

Enabling:

 
Run this program as an administrator
 

forced Windows to always start the application using an elevated administrator token.

This bypassed the initialization failure responsible for Runtime Error 91.


Why Only Some Users?

This is common with legacy desktop applications.

Possible reasons include:

  • Per-user compatibility settings
  • User profile differences
  • Legacy runtime initialization
  • Registry virtualization
  • Application startup sequence
  • Windows UAC behavior

Since only a few users experienced the problem, the issue was not related to installation files themselves.


Lessons Learned

During application migrations:

Never assume:

  • Successful file copy equals successful application migration.

Always verify:

  • Runtime components
  • Compatibility settings
  • Registry initialization
  • User-specific startup behavior

Recommended Troubleshooting Checklist

✔ Verify NTFS permissions

✔ Compare working and affected users

✔ Test application using Run as administrator

✔ Check Compatibility settings

✔ Verify registry access

✔ Compare group memberships

✔ Review recent storage migration

✔ Keep old drive available until testing completes

✔ Backup original application folder

✔ Contact software vendor before reinstalling


Best Practices During Storage Migration

  • Keep original drive until testing completes
  • Create ZIP backup of application folder
  • Preserve application data separately
  • Verify application launches for multiple users
  • Test administrator and standard users
  • Document every configuration change
  • Perform migration outside business hours
  • Validate software licensing
  • Preserve timestamps and permissions
  • Avoid deleting old storage immediately

Conclusion

This case demonstrates that application issues after a storage migration are not always caused by missing files or incorrect permissions. Legacy desktop software may depend on elevated execution or user-specific initialization behavior.

By following a structured troubleshooting process—verifying permissions, comparing user environments, testing elevated execution, and checking compatibility settings—the issue was resolved without reinstalling Windows or restoring the original drive.

Keeping a backup of the original application installation until the environment is fully validated remains one of the most valuable safeguards during any server migration project.

 

#WindowsServer #WindowsServer2019 #RDS #RemoteDesktopServices #ServerAdministration #SystemAdministrator #ITSupport #TechnicalSupport #WindowsTroubleshooting #RuntimeError91 #RuntimeError216 #GeniusSoftware #AccountingSoftware #LegacySoftware #SoftwareMigration #HDDtoSSD #StorageMigration #Robocopy #NTFS #Permissions #ICACLS #WindowsSecurity #UAC #RunAsAdministrator #CompatibilityMode #WindowsCompatibility #Registry #ApplicationError #SoftwareRepair #ServerMigration #EnterpriseIT #WindowsAdmin #BusinessSoftware #DataMigration #FilePermissions #Infrastructure #ServerMaintenance #ITInfrastructure #SystemMigration #TechSupport #WindowsTips #ITCaseStudy #SoftwareSupport #MigrationProject #BackupStrategy #StorageUpgrade #ApplicationSupport #WindowsManagement #DesktopApplications #EnterpriseComputing

Advertisement