Unbalanced parenthesis.

Open
#22 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
powershell

Research direction

Reproduce the command with the linked Validation OS ISO using ValidationOSImageBuilderCLI.exe and review the generated RunCMD logs, especially reg-load.log and reg-add.log. Trace why the registry commands emit “Unbalanced parenthesis”; done means the image generation completes without these uncaught error messages while producing a usable ValidationOS.wim.

Written by the indexing model from the issue text.

Description

While trying to use https://software-static.download.prss.microsoft.com/dbazure/26100.8972.260722-1659.ge_release_svc_prod3_amd64fre_en-us_VALIDATIONOS.iso as something like:

D:\ValidationOSImageBuilder\x64\ValidationOSImageBuilderCLI.exe `
  --generate-image `
  --output C:\WinVOS `
  --features SMB.pkg `
  --features graphics.pkg

I get a lot of output messages that seem like an uncaught error alike Unbalanced parenthesis (not sure they are related to the output that is displayed arround them):

Logging into C:\Users\vagrant\AppData\Local\Temp\1\WinVOS\out\260818-1919\Logs\RunCMD\19-36-04.77--reg-load.log

Unbalanced parenthesis.

reg load HKLM\VOS_SYSTEM "C:\Users\vagrant\AppData\Local\Temp\1\WinVOS\out\260818-1919\mnt\Windows\System32\config\SYSTEM"



Logging into C:\Users\vagrant\AppData\Local\Temp\1\WinVOS\out\260818-1919\Logs\RunCMD\19-36-05.01--reg-add.log

Unbalanced parenthesis.

reg add "HKLM\VOS_SYSTEM\ControlSet001\Control" /v SystemBootDriveLetter /t REG_DWORD /d 88 /f

It seems something is broken somewhere inside ValidationOSImageBuilderCLI.exe (or in something it calls) and looks like a bug.

Thou, the ValidationOS.wim file is generated and seems to work; thou, those kinds of messages should be handled/fixed.

Dominant language
Batchfile
Stars
31
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/Validation-OS

All issues in microsoft/Validation-OS

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.