Rui Lopes

Thanks for pointing that C# class, it cleared things up! And Indeed, using `$env:COMPUTERNAME\SQLSERVER` worked around the problem. It now correctly creates the backup files. Thank You! Despite the workaround,...

@syrusakbary oh indeed, the mapping was swapped. thank you for spotting it! the way wasmer does this is different than docker and wastime, so I was completely oblivious about the...

@jhowardmsft @PatrickLang any news about this? I've tested the current behavior from plain C applications and posted the results at [rgl/docker-windows-2016-vagrant](https://github.com/rgl/docker-windows-2016-vagrant), essentially: **Windows containers cannot be gracefully shutdown,** either there...

oh d'oh... I didn't actually implemented the (PRE)SHUTDOWN when I originally tested this! [I've updated the source](https://github.com/rgl/docker-windows-2016-vagrant/commit/9a8e75b29416ef551757a9dd0d3cebac13ccb9c2), and the service now receives the PRESHUTDOWN (but not SHUTDOWN) notification. Here's the...

@godefroi I'm not using Hyper-V. Please, see my previous comment to known what I'm using.

@darrenstahlmsft please do see the sources. there're in the [console](https://github.com/rgl/graceful-terminating-console-application-windows/), [gui](https://github.com/rgl/graceful-terminating-gui-application-windows/), and [service](https://github.com/rgl/graceful-terminating-windows-service/) repos and the dockerfiles at [rgl/docker-windows-2016-vagrant](https://github.com/rgl/docker-windows-2016-vagrant) (inside the examples directory).

Never seen that before. It seems to be a temporary state; can you modify the code to retry the operation? e.g.: ```powershell while ($true) { Write-Host 'Cleaning up the WinSxS...

you have to install the dependencies as described in the readme.

Good to known there is a workaround for the recent Fedora. The only QEMU 8.1 that I've tested with was the QEMU flavor that ships with Proxmox 8.1.3 (the `pve-qemu-kvm...

For my use-case of executing ad-hoc scripts using vagrant, when using `auto`, the scripts were immediately executed after windows boot, but they would fail due to something in Windows not...