Windows 10 to Windows 10 LAN friends are not showing up
We have 4 computers that all stopped showing LAN friends worlds at the same time. All were on 1.19.62 and have since been updated to 1.19.63 . Three computers connect over WIFI and one over wired. This was first noticed 2/23/23 but it could have been going on before then as my kids hadn't played in a week.
For trouble shooting on all computers, we have tried:
Changing to a different internet network on a different router.
Made sure network visibility and file sharing was turned on.
Minecraft worlds are set to LAN visible
Firewall is set to allow Minecraft and Network Discovery
3 of 4 computers have the latest Windows update.
Similar thing happened to me. I made a copy of my survival world, then switched in to creative. I did a few hours of building, then logged off. When I restarted the next day, I was at spawn with no inventory nor experience.
Details:
Windows 10
The world was started in 1.16
At the time it was on update 1.19.60
Frameless Glass resource pack enabled
Default mode is Adventure
Personal game mode was set to Survival when the copy was made, but switched to Creative to work on some test designs.
In Creative when it happened.
2 hours of game play in the copy
I was in the Nether
I had not destroyed my respawn point
Two days later my all my items were restored when I logged in.
I did not check my Ender Chest at the time as it I was in creative and was planning to delete the world after I picked a design I liked. Checking now all items are in my Ender Chest and Sulker Boxes.
I did log into the Survival world during this time frame and was shown the death screen when the world loaded. I was in the Nether but in a spawn proofed area. I figured a ghast had flown in and fire balled me, as it takes my computer a long time to load a world. Some times this happens when I blind travel through a nether portal. Normally if this happens I will hear myself taking damage and hear the sound of a mob while seeing the loading world screen. I didn't think or it at the time but maybe this was related to the bug so I thought I would add it here.