Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote reboot logic is broken when targeting Windows 11 machines #487

Open
Baune8D opened this issue Dec 1, 2021 · 0 comments
Open

Remote reboot logic is broken when targeting Windows 11 machines #487

Baune8D opened this issue Dec 1, 2021 · 0 comments
Assignees
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended
Milestone

Comments

@Baune8D
Copy link

Baune8D commented Dec 1, 2021

What You Are Seeing?

Whenever Boxstarter tries to restart the machine remotely, it will reconnect the Powershell session before the restart actually happens, which leads to failure.
image
Boxstarter correctly detects the severed remote session as the restart is triggered, but will reconnect (see the red arrow in the image) before the machine actually restarts (still on the restarting splash screen), which ultimately leads to the I/O error in the image.

What Is Expected?

The machine is supposed to wait with reestablishing remoting until machine has fully rebooted.

How Did You Get This To Happen? (Steps to Reproduce)

Trigger a remote install using the following command: Install-BoxstarterPackage -ComputerName $hostname -PackageName $package -Credential $cred -StopOnPackageFailure and triggering a restart from within the BoxStarter package with Invoke-Reboot

Output Log

@Baune8D Baune8D added the Bug Issues where something has happened which was not expected or intended label Dec 1, 2021
@mwallner mwallner self-assigned this Feb 16, 2022
@mwallner mwallner added this to the 3.0.1 milestone Apr 12, 2022
@mwallner mwallner modified the milestones: 3.0.1, 3.1.0 Nov 17, 2022
@mwallner mwallner modified the milestones: 3.1, 3.2 Jun 6, 2023
@pauby pauby added the 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue label Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended
Projects
None yet
Development

No branches or pull requests

3 participants