Solved Unable to connect to update service after Insider (Dev) Updates

On 3/9 I did a routine update to my Win 11 Insider (Dev) to 25314/230303-1411 and ever since 3/15 my Insider VM will no longer connect to the update service. It says I'm not connected to the internet, which I am since all other communications are working fine. This "update" series included Windows Insider Preview 25314.1000 on 3/9, an update to the stack package 1101.2303.2011.0 on 3/15, and an update to the Malicious Software Removal Tool x64-v5.111 also on 3/15. I'm inclined the think the problem as associated with the Stack package update since this seems to be associated with windows updates.



Has anyone else had this problem?

An, more imporrtantly anyone have any ideas on how to fix it?

Thanks,

Jabiru

Is the VM sharing the internet connection with the host?
How are the adapters configured? Is is NAT or is it bridged?
Are you able to run update to the MSStore on the hosted system? Mail?
Also,, Is your host system updating OK?
Why not roll back to the time prior to when you started having the issue?

Wow, ok, lots of questions.....

I'll go through them one at a time.

1. Yes, the guest is sharing the internet with the host. The guest has an IP address of 172.24.173.6 with a subnet mast of 255.255..240.0 running in DHCP for both the IP and DNS. I am assuming with those settings it's using NAT.
2. MSStore use is normal, connects, downloads and installs apps with no trouble.
3. Host system updates with no problems.
4. Not too sure rolling back is going to "fix" the problem, I'm more interested in finding out how & why it happened.

Ok, I think I've figured out what happened. I was on the Insider DEV channel and my last update was build 25314. Then MS split the DEV Channel and created the Canary Channel which has the same bulid numbers as the old DEV channel. The "new" DEV Channel has build numbers the 23XXX range. I suspect that my Windows Update is trying to connect to the Canary Channel and I'm not registered in that channel. I suspect I'm going to have to do a cold load of the DEV channel latest build in order to get the correct build number for a DEV channel update.

Any thoughts?

Yes, it was never a connection problem.
You should have been switched automatically to Canary but as you suspect since it is a VM and therefore not always active,
the switch did not occur.
I suggest you force select Canary, that is if you want to go that route.

OAT said:

Yes, it was never a connection problem.
You should have been switched automatically to Canary but as you suspect since it is a VM and therefore not always active,
the switch did not occur.
I suggest you force select Canary, that is if you want to go that route.

Click to expand...

Yeah - sometimes you have to relink MS account to select Canary.

Occasionally, you do not see any options at all and you have to turn Flightsigning on.

In worst case, you can create a canary iso with uudump and upgrade manually.