Windows 10: WinXP machine doesn't see Win10 machine after version 1903 update

I have 2 machines on a network (WinXP Sp-3 & Win10). After the update, my Win10 machine still sees my WinXP machine (i.e. I can copy files back & forth while on my Win10 machine).

However, my WinXP machine doesn't see Win10 anymore. When I try to see my Win10 documents & desktop from a shortcut icon on WinXP, I get the message below.




When I try to remap Drive V, using the following:



I get this message:



I don't have a password on either computer, but I was able to have both computers see each other before. Any idea on how my WinXP computer can see my Win10 computer?
Thank you in advance!

:)

 

Updating machines through one machine

If you did that, how would MS know that each version of windows you want to update is legit? Also, there will be small differences between machines in terms of updates unless they are identical - driver updates for example.

You can certainly let several machines connect through one particular machine, but since each one needs to be validated and may have slightly different dl packages, I don't see any way to dl just what you need to one machine and then have it be distributed to it's client machines.

Maybe in an enterprise environment. MS might have server software that can do something like that, but I doubt they're going to let you do it under any consumer version of windows.

 

Updating machines through one machine

Is there a way to update a set of machines through one machine instead of each machine downloading windows updates?

 

Hyper-V machine freezes on start after 1903 update

Since updating OS to version 1903, my Hyper-V machines freeze at start for about 20 seconds, then re-open login page, then it boots fine and all is good.

I've updated graphics drivers, gone through several Windows-based scans, i.e. sfc /scannow, etc.

I've also tried...

Stopped/restarted Container service

Disabling/re-enabling Hyper-V

Any suggestions?

My build:

i7-8700

32GB RAM

Win 10 Pro 1903