[smileybarry]

Are you referring to bridged adapter settings? It could just be a VMware limitation when they reimplemented their Windows hypervisor to work with Windows Hypervisor Platform (I.e. mini Hyper-V), so they could work with Credential Guard / WSL2 enabled. There’s a bunch of initialization work on every boot because of how the Hyper-V adapters are configured (which I hate) so VMware might be tearing adapter bridges/vSwitches down & remaking them each boot.

Or if you mean IP ranges and such then that shouldn’t happen in either mode, or at least it doesn’t seem to happen to any of us at the office on Workstation 16/16.2/17. (and VMware asking for elevation to change some adapter settings is a design choice by VMware)

[moremetadata]

> bridged adapter settings? Yes.

> There’s a bunch of initialization work on every boot because of how the Hyper-V adapters are configured (which I hate) so VMware might be tearing adapter bridges/vSwitches down & remaking them each boot.

It resets everytime the main windows os is rebooted so it sound like this.

Like I said, I've never seen settings behind UAC prompts being reset, I've seen settings being reset by windows updates, but never something like this on a day to day basis.

[smileybarry]

It’s just Hyper-V itself deleting and recreating switches & vNICs. It’s the same root cause as that issue where your Ethernet adapter gets a “(2)” or “(3)” tacked on, like in this (3rd) issue: https://learn.microsoft.com/en-us/answers/questions/326293/h...