Files

T

kawa 403a0a5e69 fix(10-02): record RTVAL-01 fail — Intune cannot parse generated .intunewin

- RTVAL-01 status set to FAIL: Win32 app wizard fields stayed empty, OK greyed out
- Verbatim technician symptom quoted verbatim in report
- Interpretation: Detection.xml / package metadata malformed or missing in .intunewin archive
- RTVAL-02, RTVAL-03, RTVAL-04 marked BLOCKED (all depend on RTVAL-01 PASS)
- ISSUE-01 raised in Issues Found with root cause hypothesis and resolution path
- Plan 10-02 stopped; gap-closure cycle required before retesting

2026-04-13 11:38:53 +02:00

3.9 KiB

Raw Blame History

Runtime Validation Report — ImpTune v1.1

Status: BLOCKED — RTVAL-01 FAIL; plan 10-02 stopped at task 1; gap-closure required before resuming Started: 2026-04-13 Signed off by: Signed off date:

Tenant & Environment

Field	Value
Intune tenant (domain)	arescom.fr
Test device hostname	ARES-5CG5220YTM
Windows OS build	26200.7171
Device is Intune-managed	yes
Driver vendor(s) tested	ricoh.zip

PCL6 Driver for Universal Print | | ImpTune commit SHA | 1c3f458583 | | Package file name | Copieur_2eme.intunewin | | Package SHA256 | 0aac31ff190d21cbb4c76a81d4ad32657a5a3298e7e3fcc79a080e87cf40c333 | | Generated at | 2026-04-13 |

RTVAL-01 — Tenant ingestion

Status: FAIL Tested: 2026-04-13 Evidence: No screenshot captured — the Intune upload form never reached a populated state. UI remained empty; there was no visible error banner to screenshot. Verbatim symptom (technician): "The intunewin package cant be uploaded, the OK button is greyed out and none of the fields (name, platform, size, mam enabled) gets populated." Interpretation: Intune accepted the file transfer but was unable to parse its embedded Detection.xml / package metadata. The Win32 app creation wizard stalls in this state when the .intunewin content manifest is malformed or when the embedded detection.xml is missing or structurally invalid. This is a structural defect in the package that ImpTune is generating — exactly the runtime gap RTVAL-01 is designed to catch. No portal error banner was shown because the failure occurs silently during client-side metadata extraction. Package tested: Copieur_2eme.intunewin (SHA256 0aac31ff190d21cbb4c76a81d4ad32657a5a3298e7e3fcc79a080e87cf40c333, ImpTune commit 1c3f458)

RTVAL-02 — Install under SYSTEM (pnputil + $PSScriptRoot)

Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:

RTVAL-03 — Detection rule reports Installed

RTVAL-04 — Uninstall under SYSTEM

Issues Found

ISSUE-01: .intunewin package metadata unreadable by Intune Win32 app wizard

Discovered: 2026-04-13 during RTVAL-01
Severity: Blocker — prevents all downstream RTVAL checks (02, 03, 04)
Symptom: Win32 app creation wizard fields (name, platform, size, MAM enabled) remain empty after file upload; OK button stays greyed out; no portal error shown
Root cause hypothesis: Detection.xml embedded inside the .intunewin archive is missing, malformed, or uses an unexpected schema version. The IntuneWin32App packager requires a valid detection.xml at the root of the archive alongside the content folder.
Affected file: Copieur_2eme.intunewin (evidence/Copieur_2eme.intunewin)
Affected code: ImpTune .intunewin generator (commit 1c3f458)
Resolution path: Debug the generator to verify Detection.xml is being created, embedded, and follows the expected Intune Win32 app manifest schema. Recommended: run /gsd:debug on the .intunewin generator, OR let phase verification surface this as a gap and use /gsd:plan-phase 10 --gaps to draft a gap-closure plan.
Status: Open — plan 10-02 stopped; gap-closure cycle required before retesting

Sign-off

All five RTVAL criteria PASS or have documented rationale
Evidence files committed under evidence/
Signed by: ___________________

3.9 KiB Raw Blame History