This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 21%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES8%3C/text%3E%3C/svg%3E)
We have a few lab servers. Some have been fresh physical installations, some in-place upgrades from working 2019 configurations and the same as VM's. All seem to show the ethernet connections as metered.
registry keys for costs dont seem to have any impact. the GUI option dont work either!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 53%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
Same issue. Clean install of 2022, Set as metered connection is set to Off on Ethernet connection (current network), value in Registry key DefaultMediaCost is set to 1.
Windows still claims that I'm on a metered connection.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 17%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
I have the exact same issue. Have you found a solution for this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 36%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPB%3C/text%3E%3C/svg%3E)
I have exactly the same issue. Windows Server 2022 Standard (Desktop Experience) fresh install and the Network Connection reports it is a metered connection. Metered connection slider is set to off and registry value for DefaultMediaCost (Default/LAN/WiFi) set to 1. I don't know if it's just a display error or if it's really seeing the connection as metered. How do you test???
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 32%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECW%3C/text%3E%3C/svg%3E)
Exactly same here.
The registry looks normal.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]
"3G"=dword:00000002
"4G"=dword:00000002
"Default"=dword:00000001
"Ethernet"=dword:00000001
"WiFi"=dword:00000001
Still no solution...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUO%3C/text%3E%3C/svg%3E)
We have same issue across 11 different Windows Server 2022 Standard with desktop experience. Have not found a solution for this yet; it happens on fresh installs, even on domain controllers which is really weird.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 17%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
same here brand new OEM copy of srv 2022 fresh out the box with HyperV and SET switches etc.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Might check here and with server manufacturer about support for Server 2022.
https://www.windowsservercatalog.com/
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hello SimonSupportStack,
Thank you for your question.
I would suggest you check Gateway and DNS ips on this 2022 and make sure there is no Latency or Ping time out.
Also please check if you any Wireless adapter installed on this server.
Please check registry from below links and compare with your 2022 server and revert it to original value.
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/how-to-set-an-ethernet-connection-as-metered-to/ecdaca08-d413-4a6a-9e33-b4afb337fc18?auth=1
--If the reply is helpful, please Upvote and Accept as answer--
We ended up on a PSS call. After much back and forth we were told ‘it’s by design’ - in fairness it does seem to be a GUI issue not a functionality issue.
bit like the windows 10 screens in server 2022 setup I guess. Bit tardy imho.
mystery closed!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 19%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I disagree with "...it does seem to be a GUI issue not a functionality issue..". It seems in fact to disable the download functionality in WSUS under Server2022. So that WSUS is in the end not anymore usable as an virtual server Feature under server 2022 on an ESXI.
Mystery not closed
Microsoft PSS told me that. It's not my opinion, its what i was told. read the post.
Where in my comment did I give you the feeling I am referring to your opinion? Read my post!
So please come back to the thread. And it is not useful since usenet times to end a urgend questioning post comment with the word "closed" if it only refers to not helpful answers from microsoft.
Are here any updates? Because like I commented the wsus does not function anymore under server 2022 if in VMWare. Same with the intel virtualisations. After fresh install network is usable as normal network and wsus downloading updates. After a time the network connection is switched to metred and the downloads stop. No possibility to set it back to non metred. You have to disconnect the machine put a new vritual network card in it and it will start working for a while.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 68%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETL%3C/text%3E%3C/svg%3E)
I was able to solve it. I tried removing the adapter and adding a new one and everything worked as long as the adapter was set to DHCP. I set the MAC to static and made a reservation in my DHCP Server. I am using the Sep 2021 iso for Server 2022. I will see if updates let me enter a static IP on the NIC>
I was able to solve it. I tried removing the adapter and adding a new one and everything worked as long as the adapter was set to DHCP. I set the MAC to static and made a reservation in my DHCP Server. I am using the Sep 2021 iso for Server 2022. I will see if updates let me enter a static IP on the NIC.