Original used 'echo %BIOS_STATUS% | findstr /C:"->"' to detect whether check-bios.cmd actually applied a firmware update. The '>' inside the value (from check-bios writing e.g. 'updated 1.5.0 -> 1.6.0') gets parsed by cmd.exe as a redirect operator BEFORE the pipe is set up. Result: echo wrote a file named '1.6.0' in cwd instead of piping to findstr. findstr saw no input, returned errorlevel=1, block never fired. Plus a stray file got created in X:\Windows\System32. Confirmed empirically in the win11 VM with test bat: - echo|findstr approach: SKIPS even when '->' present (bug) - substring-replace: FIRES iff '->' present (correct) Fix: replace echo/pipe/findstr with a substring-replace test: call set "BIOS_STATUS_STRIPPED=%%BIOS_STATUS:->=%%" if not "%BIOS_STATUS%"=="%BIOS_STATUS_STRIPPED%" ( ... ) The '>' inside %VAR:->=...% is parsed as part of the substring substitution token, not as a redirect. Yields true diff only when the arrow was actually in BIOS_STATUS. xcopy region was never impacted by the bug because subsequent if-exist blocks didn't depend on the previous errorlevel state. But the BIOS sub-stage push to the dashboard was silently broken. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
16 KiB
16 KiB