psadt-deploy-skill 0.26.4 → 0.26.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -369,6 +369,30 @@ pre-flight fails on non-ASCII without a BOM), and anything that lands in a packa
|
|
|
369
369
|
Recent releases below; the complete history is in **[CHANGELOG.md](CHANGELOG.md)** (nothing is ever removed
|
|
370
370
|
from either).
|
|
371
371
|
|
|
372
|
+
### 0.26.6 - 08.09.2026
|
|
373
|
+
- **Fixed: the sandbox host timeout force-killed the viewer, then told you to close the window.** A timed-out run
|
|
374
|
+
was torn down like a finished one. That **orphans `vmmemWindowsSandbox`** — the Hyper-V compute service owns it,
|
|
375
|
+
so the host cannot kill it, and it keeps the work folder locked until the next run throws on it — and it removes
|
|
376
|
+
the only window through which the guest could still be shut down cleanly. The script's own comments name this
|
|
377
|
+
mechanism as the reason the *guest* must shut itself down; the timeout path did it anyway. A timeout now touches
|
|
378
|
+
nothing and explains what to close and which knob to raise.
|
|
379
|
+
- **Fixed: the warning claimed 60 seconds while the code waited 180** — a literal duplicating a parameter default.
|
|
380
|
+
One declared value now feeds both.
|
|
381
|
+
- **Appendix G finding 6 corrected**: "no recovery path" is now scoped to a run killed from *outside* the script.
|
|
382
|
+
### 0.26.5 - 08.09.2026
|
|
383
|
+
- **L.8, new: MSIX/AppX**, verified against Microsoft Learn and against the live cmdlets. MSIX is a two-step
|
|
384
|
+
model — machine-wide **staging**, then **per-user registration at logon** — and three traps follow from it:
|
|
385
|
+
**`Add-AppxPackage` as SYSTEM registers the app for the SYSTEM account and reports success** (nobody can launch
|
|
386
|
+
it), **`Get-AppxPackage` is the wrong detection cmdlet** (finds nothing right after provisioning, so Intune
|
|
387
|
+
reinstalls forever), and **de-provisioning does not remove the app from existing users** — a complete uninstall
|
|
388
|
+
needs `Remove-AppxProvisionedPackage` *and* `Remove-AppxPackage -AllUsers`. Plus signing: the certificate
|
|
389
|
+
Subject must equal the manifest Publisher (so a vendor MSIX cannot just be re-signed), self-signed certs belong
|
|
390
|
+
in `LocalMachine\TrustedPeople`, and missing timestamping is what makes an expired certificate break installs.
|
|
391
|
+
And the decision that comes first: **usually don't wrap MSIX in PSADT** — Intune takes it natively.
|
|
392
|
+
- **L.9, new: App-V is not end of life.** The client and sequencer are **no longer deprecated** (fixed extended
|
|
393
|
+
support, no end date, no extra cost); only the **server components** end in **April 2026**. Also: `-Global` is
|
|
394
|
+
the device-context switch, and a package in use goes *pending* — a global task applies only after a restart.
|
|
395
|
+
- **The MSIX row in L.2 was misleading and is rewritten**; L.2 gains an App-V row.
|
|
372
396
|
### 0.26.4 - 08.09.2026
|
|
373
397
|
- **L.7, new: Inno Setup and NSIS**, verified against vendor documentation. `/VERYSILENT` **reboots the
|
|
374
398
|
machine by itself** when a restart is needed — so `/NORESTART` is mandatory, and `/RESTARTEXITCODE=3010`
|