Boosted+ POS Windows public beta 1 — Version 1.0.24, Build 34

Official download and current instructions:
https://boostedpos.online/download
https://boostedpos.online/download/windows/help

SIGNING AND VERIFICATION
This beta uses the existing self-signed Boosted Technologies certificate.
Installer SHA-256: 2de84acd812090c67e8cf696f6922b1184cdfc0dfb1065856ce6a06f08761177
Certificate thumbprint: F77E6890E1B8281453FCD2773830373C6E0CD6D3
Check all 64 characters of the installer hash with:
Get-FileHash -Algorithm SHA256 .\BoostedPlus-1.0.24-34-windows-x64.exe

Open the .cer file and check Details > Thumbprint. If it differs, stop.
The computer administrator can import this exact certificate into Local Machine > Trusted Root Certification Authorities, then Local Machine > Trusted Publishers. This authorizes this publisher on the PC; it is not a public certificate-authority endorsement. Never import a different certificate to force an install.
Right-click the installer > Properties > Digital Signatures and verify Boosted Technologies and its certificate chain.

WINDOWS SECURITY PROMPTS
SmartScreen: after verifying source, hash and publisher, choose More info > Run anyway if Windows offers it. Keep SmartScreen enabled. An administrator-managed policy may prevent continuation; ask IT.
Smart App Control is a separate Windows 11 feature and may still block a self-signed application. If the computer owner elects to turn it off for this beta, open Settings > Privacy & security > Windows Security > App & browser control > Smart App Control settings > Off. Read the device warning first. This reduces protection for the whole PC. On some Windows builds, turning it on again requires a reset or Windows reinstallation; do not assume this is a temporary switch. Keep Defender antivirus and the firewall enabled. Managed PCs require their IT administrator.
Microsoft references:
https://support.microsoft.com/en-us/windows/security/threat-malware-protection/smart-app-control-frequently-asked-questions
https://learn.microsoft.com/en-us/windows/apps/package-and-deploy/smartscreen-reputation
https://learn.microsoft.com/en-us/windows/apps/develop/smart-app-control/code-signing-for-smart-app-control

FRESH COMPUTER
After verification, run the installer as administrator. Choose the existing business and correct branch during setup. Do not create another business to attach a computer.

EXISTING MAIN BRANCH COMPUTER
Do not uninstall, delete ProgramData branch files, reset the branch or register it again.
1. Stop sales on its connected tills. Upload offline work and allow cloud outcomes to be acknowledged. Zero awaiting upload does not necessarily mean posted.
2. Resolve outstanding Windows sync reviews on the web, beginning with the earliest sequence. Original overlapping openings and later cash closures need the business’s cash review; this installer does not approve them.
3. Reconcile and close the local till with verified cash after checking both web and Windows transactions. Confirm backup protection is configured.
4. Close Boosted+ on connected computers. Extract this entire ZIP to one folder on the main service PC.
5. Open Windows PowerShell as administrator, change to the extracted folder and run:
   .\Update-BoostedPlus-Beta34.ps1
   The helper is signed. It verifies this exact installer, waits for the existing service to create a fresh protected backup and safe update point, then activates the installer. If policy requires it, launch PowerShell with -ExecutionPolicy AllSigned; do not disable signature checks.
6. An open till, unacknowledged work, missing backup protection or quarantined earlier failure will defer the update. Follow the reported reason; do not edit protected update files or force-stop the service.
7. Reopen Boosted+, check Version and updates = 1.0.24 / build 34, confirm the original branch, then check customers, units, categories and the shared till.

To check only the helper and package without installing:
.\Update-BoostedPlus-Beta34.ps1 -VerifyOnly

The installer will not downgrade or reinstall an equal/newer build. Fresh installations may run the EXE directly; existing branch services require the protected update path. This build does not enable an automatic update feed.

Keep one shared till per physical drawer. Sync before closing; choose one closer. Use separate tills for separate drawers. Do not recreate held sales to clear a conflict.
