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!

For a Win XP machine to be able to see a Win 10 machine Windows 10 must have the SMB 1.0/CIFS Server enabled in Windows Features. If the update was the 1903 feature update it probably reset it to the default (turned off).




Turn Windows Features On or Off in Windows 10

phrab said:

I just went to my user folder "Phil">Properties>Sharing & see that I haven't put any names for sharing down. I don't want to share it with "Everyone", since it's an administrative profile, but can I specifically name just my WinXP user profile. If so, I'm not sure how to find that.

You cannot select a user profile from another machine when setting share permissions, you can only select user names that exist on the Windows 10 PC that is doing the sharing.

If your account on the XP machine has the same name as an account on the Window 10 machine then when you connect to the W10 share you will have the same permissions as the local W10 account. Assuming your account name is 'Phil' on both the XP and W10 PC then when \\XP\Phil connects to the W10 share it will have the same permissions as the local \\W10\Phil account.

If you sign in with a different name on the XP machine, then you can choose to map a network drive connecting using a different name so that you can connect as Phil.

User profile folders have special NTFS permission set and you can't even access them if your on the PC

bro67 said:

smbv1 server and client have to be enabled on the W10 Machine. The net use command can be used to map shares.

Thank you. I had already done that. After reading everyone's replies & advice (& looking back at my previous post & it's answers), I've decided that it's unnecessary to link to my entire profile. I'll mark this thread solved.

- - - Updated - - -

Samuria said:

User profile folders have special NTFS permission set and you can't even access them if your on the PC

Thank you, but I'm not sure what you mean. I have 2 profiles on my Win10 machine: Phil & Phil 2003. Phil has administrator rights & can access Phil 2003.

- - - Updated - - -

Bree said:

You cannot select a user profile from another machine when setting share permissions, you can only select user names that exist on the Windows 10 PC that is doing the sharing.

If your account on the XP machine has the same name as an account on the Window 10 machine then when you connect to the W10 share you will have the same permissions as the local W10 account. Assuming your account name is 'Phil' on both the XP and W10 PC then when \\XP\Phil connects to the W10 share it will have the same permissions as the local \\W10\Phil account.

If you sign in with a different name on the XP machine, then you can choose to map a network drive connecting using a different name so that you can connect as Phil.

Thank you for your explanation. After reading everyone's replies & advice (& looking back at my previous post & it's answers), I've decided that it's unnecessary to link to my entire profile. I'll mark this thread solved.

phrab said:

Thank you, but I'm not sure what you mean. I have 2 profiles on my Win10 machine: Phil & Phil 2003. Phil has administrator rights & can access Phil 2003.

Probably meant that by default a user doesn't have permission to see another user's profile folder. As an administrator Phil would have been asked if you want to gain permanent access when you first tried to open Phil 2003's profile. When you said 'Yes' then your Phil account was added to the permissions for the Phil 2003 folder.