"Reboot" button in setup after a repair does nothing

[UweKeim]

Description

Having used the "Repair" option of Hosting Bundle 3.1.19 and Hosting Bundle 5.0.10 they both showed a "Reboot" button on some systems.

(Context was this issue)

Whenever I clicked the "Reboot" button, exactly nothing happend. Neither did the system reboot, nor was an error message shown.

This is a screenshot of on a German system ("Neu starten" is the reboot button).

In the end, I did a manual reboot.

Configuration

OS: Windows Server 2019 German

Expectation

I did expect that when clicking the "Reboot" button, the system actually reboots.

Update 1

On some systems, the "Reboot" button actually works correctly. So this doesn't seem to be a general issue.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[danmoseley]

thanks @vcsjones -- infrastructure-installer relates to eg the build of src\installer. area-setup is the product.

having said that I actually don't know whether this should be here or in the SDK repo -- @NikolaMilosavljevic ?

[adityamandaleeka]

@wtgodbe Can you please investigate?

[wtgodbe]

@UweKeim I've been unable to reproduce this, would you be able to upload setup logs from the repair of 3.1.19? They should be in C:\Users\<username>\AppData\Local\Temp

[UweKeim]

I've tried to recognize the server where this happened, but am not sure whether I found the right one. I've checked several once and only found one with actual log files in C:\Users\<username>\AppData\Local\Temp.

I've attached them here:

dotnet5-server1.zip

Looking through them it seems that everything worked correctly, so I'm really unsure whether these are the erroneous log files.

---

Update 1:

I've found yet another server with log files. Again, still not sure whether this is the one with the failed reboot:

dotnet5-server2.zip

[adityamandaleeka]

@UweKeim I just looked at this. We don't do anything interesting here; the behavior just comes from WiX (the installer toolset).

I think this issue might be what you were seeing: wixtoolset/issues#6145

[ghost]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.