Unexpected results when BDS files not completely updated

Getting a good handful of servers that have this bug

I have same issues, new worlds or unexplored chunks in existing worlds, turns all in stone.

Same issue here, two different bedrock servers. Exploring new worlds changes the WHOLE world to stone for most users, caused my player to spawn in a black void with chunks of terrain and pillars off in the distance. I think I'm facing up, since changing the weather to rain is causing it to rain from directly in front of me. I think maybe I'm in Inception. 

I have a LOT of freaking out elementary school kids that have been working on a server for the entirety of the pandemic who just watched their world turn into rocks. 

I think Bedrock server is being taken too literally here. 

What OS are you using? I just started up a new 1.16 server on Windows and world generation seems to work as expected.

Given how much this could impact servers it would be helpful if we can narrow down the cause.

Others are reporting this is caused by addons. Try removing all addons from the client and server and test again (not sure if its client side and just visual or server side as well).

I have the same issues and can clarify that I have a purely vanilla server. No addons at all.

Just upgraded the world today and every unexplored area is stone.

Not sure if this helps, but here's the world seed -790499067012621130

We've lost two worlds to this issue.

Please resolve ASAP

I've tried every setting change I can think of and have been unable to produce this issue.

If someone could upload an affected world it may help. Size limits on Mojira are restrictive so its usually best to upload to a service like OneDrive/Google Drive and provide a link.

Edit: Understanding how you upgraded to 1.16 may help too. Did you just copy the new files over the old ones or did you selectively migrate the world and server.properties into a new folder with 1.16?

Confirmed on our server with no addons. Existing world - new chunks are created as stone (especially noticeable in ocean biomes!). When I import the a server backup from before the 1.16 update into the Windows 10 client the chunks generate just fine so this I think is specific to the Bedrock Server. 

I am having the sam issus and noticed it in the nether where the lava is generated as red water.

I am using the ubuntu version of the Server. Our server has not had the most recent update 1.14.60.5 it was 1.14.60.2 . We are not using any addons. 

This is the Bedrock Worlds Server File before any new chunks are generated. So my Backup before the Update: https://cloud.wieser.myhome-server.de/s/rMe4ZRGKrbr77Fj

I upgrade the Server by just replacing the Old bedrock_server file with the new one of 1.16.0.2

To mention i had problems with disappearing chests mentioned here https://cloud.wieser.myhome-server.de/s/rMe4ZRGKrbr77Fj 

If you need all server files or the world with infected blocks let me know.

Replacing just the bedrock_server file isn't enough.

Can you see if the same issue is experienced if you migrate your server.properties and world files into a new extract of the full 1.16 server files? There is a bunch of supporting files in the update that you wouldnt have updated by just moving the executable.

I realise this behaviour works in Java but the two are vastly different.

Based on the comments I've managed to reproduce this by just copying the 1.16 EXE into the existing BDS install.

This is not how an application like this works. The EXE also needs all of the supporting files it is provided with.

For someone affected please try instead, unzipping the 1.16 files into a new folder and moving the server.properties and worlds folder into the new files. Please comment back if that resolves your issue.

My world was brand newly generated when I got this, I didn't just update a current one. I tried with 3 different seeds (2 random and 1 known) and got this same issue with all of them.

I encountered the same Issue on my server. You need to copy over all the 1.16 file to the current one. Behaviours and all. After doing that, it fixed my nether.

For me this solved the issue 

Samuel Ruff The world can be brand new or upgraded, in this case the world and when it was created is immaterial. The issue is the BDS files themselves.

Are you using a brand new download and unzip of the 1.16 BDS files or did you grab the bedrock_server executable and copy it into an old BDS folder.

How do we fix this if our Dedicated Servers are hosted from a 3rd party?

And what about those who rent a server?

I would suggest contacting the support line for those providers and find out if they can investigate for you.

It sounds like they've tried to integrate Bedrock into their existing Java game panels (except instead of replacing the server.jar they're replacing the bedrock_server file).

At the moment this is the only way I've been able to reproduce the issue.

Problem solved, thanks)

For those who rent a server:

1)To fix this error, you need to download the worlds folder to your device via FTP, download whitelist.json if you use it server-properties.json and permissions.json

2)As soon as you download it, click on the server menu to clear (Restore the server to its original state), and after that you will see all the files, provided that you already had 1.16 kernel installed before cleaning

3)And then upload to the server those files that were previously downloaded.

Fixed on server.pro free server, here were my steps:

1: go to the ftp tab, open the ftp link in windows explorer
2: copy worlds folder, whitelist.json(if needed), server-properties.json and permissions.json to a local folder
3: go to the reinstall tab, select "yes" in the "remove files" dropdown, click reinstall and confirm reinstall
4: copy back the files copied onto local system, replacing the files in the ftp, game should now be fixed

Will replacing the worlds folder with the new update delete the previous world? Is it possible to copy over part of the old world over as well?

Thank you for your report!
However, this issue has been closed as Invalid.

As mentioned in this comment, the issue should not exist if the server files are correctly installed.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki