Share_Manager v1.1.2

Highlights

Robust Persistent Mapping
- New "Persistent Mapping" option in Preferences (GUI and CLI).
- Persistent mapping now uses a secure, fault-tolerant logon script in the user's Startup folder.
- Credentials are securely stored and decrypted at logon; mapping is retried and logged for reliability.
- No more "username or password is incorrect" after reboot; always uses latest config/credentials.
Improved User Experience
- Status bar added to GUI, styled to match Windows conventions.
- Preferences dialog and CLI menu now immediately reflect changes.
- Initial configuration in GUI matches the old script’s user experience, including credential handling and feedback.
- Custom credential form in GUI for reliability and better UX.
Security and Reliability
- Credentials are AES-encrypted and never stored in plain text.
- Logon script and launcher are robust: handle missing config, network delays, and log all actions.
- All user-facing strings are ASCII-only (no unicode).
Bugfixes and Refactoring
- Fixed all PowerShell parser errors and improved error dialogs.
- CLI and GUI are now robust, user-friendly, and consistent.
- Removed all manual logon script management; handled automatically.
- Improved logging and log rotation.

Download the latest Share_Manager.ps1 and replace your existing script.
Run the script as usual. On first run, you’ll be prompted to configure your share, drive letter, and credentials.
Use the Preferences menu to enable persistent mapping if desired.

No administrator rights required.
GUI mode requires PowerShell with -STA.
All configuration and credentials are stored securely in %APPDATA%\Share_Manager.

Full Changelog: V1.1...V1.1.2