Fix incorrect timeout causing WSL1 OOBE to fail if the OOBE process takes longer than 30 seconds #13517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
If the OOBE process for a WSL1 distros takes more than 30 seconds, we'll hit the
LAUNCH_PROCESS_DEFAULT_TIMEOUT_MStimeout which will cause the channel to be closed, which will fail the OOBE, causing all sorts of issues.This change removes the timeout for this specific transaction, so we don't fail WSL1 OOBE if it takes more than 30 seconds to complete
PR Checklist
Detailed Description of the Pull Request / Additional comments
This issue could cause OOBE failures looking like this:
Validation Steps Performed