Unable to start

Try right clicking the executable and clicking "Run as administrator".

Alternatively, try running it with a brand new world. If that works it could be your world files are corrupted, loading them in singleplayer can trigger an auto repair that may help.

Try right clicking the executable and clicking "Run as administrator".

Alternatively, try running it with a brand new world. If that works it could be your world files are corrupted, loading them in singleplayer can trigger an auto repair that may help.

I tried to "Run as administrator", but the problems still remain.

I tried to "Run as administrator", but the problems still remain.

The method you mentioned cannot be solved, and I am a brand new server

The method you mentioned cannot be solved, and I am a brand new server

We'll need a server and world files upload to investigate any further.

I've built a new Windows 10 and Server 2016 box and the server worked on both so there's likely other factors at play.

We'll need a server and world files upload to investigate any further.

I've built a new Windows 10 and Server 2016 box and the server worked on both so there's likely other factors at play.

LevelDB error could mean that your world files are corrupted

LevelDB error could mean that your world files are corrupted

I deleted the world, and the same is true for regeneration. I don’t think this is a problem of the world, and there are other people who have feedback on this problem.

I deleted the world, and the same is true for regeneration. I don’t think this is a problem of the world, and there are other people who have feedback on this problem.

You can watch the video I uploaded.

One is 1.16.0, one is 1.16.0 compared with 1.14.60

You can watch the video I uploaded.

One is 1.16.0, one is 1.16.0 compared with 1.14.60

Had the same issue. Installed latest Windows Server 2016 updates and was able to start the server correctly

Had the same issue. Installed latest Windows Server 2016 updates and was able to start the server correctly

Thank you for your answer, I can start after the update.

Thank you for your answer, I can start after the update.

It sounds like the issue was resolved for Windows Server 2016, however, the issue persists with Windows 10 even after all updates.

It sounds like the issue was resolved for Windows Server 2016, however, the issue persists with Windows 10 even after all updates.

Starting from 1.16.0, the server can be hot backup, I suspect it is related to this

Starting from 1.16.0, the server can be hot backup, I suspect it is related to this

For those still affected, what version of Windows 10 are you running. I'm not able to reproduce this.

For those still affected, what version of Windows 10 are you running. I'm not able to reproduce this.

BDS-6413 ，Windows 10 Enterprise 2016 LTSB

BDS-6413 ，Windows 10 Enterprise 2016 LTSB

Windows 10 2016 LTSB does not meet the system requirements so would not be a valid bug report.

Windows 10 2016 LTSB does not meet the system requirements so would not be a valid bug report.

Then there is no problem, but I am surprised by the original mirror of Server 2016.（Do not update）. Support 1.14.60, suddenly not support 1.16.0. You must upgrade the patch to use it. After all, many people are renting vps and are usually not used to updating the system.

Then there is no problem, but I am surprised by the original mirror of Server 2016.（Do not update）. Support 1.14.60, suddenly not support 1.16.0. You must upgrade the patch to use it. After all, many people are renting vps and are usually not used to updating the system.

To fix the problem of wnserver2016, patch KB4103723 needs to be updated.

But I have a few friends who failed to update this patch, only updated the latest patch KB4562561 can not solve the problem of unable to open the service.

I found that if the KB4103723 patch cannot be updated, there seems to be no chance to try again. This will cause this system to no longer be able to use BDS1.16 unless you upgrade server2019 or reinstall the system and try to update

To fix the problem of wnserver2016, patch KB4103723 needs to be updated.

But I have a few friends who failed to update this patch, only updated the latest patch KB4562561 can not solve the problem of unable to open the service.

I found that if the KB4103723 patch cannot be updated, there seems to be no chance to try again. This will cause this system to no longer be able to use BDS1.16 unless you upgrade server2019 or reinstall the system and try to update

It's fixed! For anyone who has Windows 10 and has the same issue, I am not sure which Windows update fixed it, however, I removed the last 4 updates Windows did and re-installed them.

I had to download the updates directly from the Microsoft website myself, though if you can use Auto-Update do that instead to re-install. Windows Update had an issue running on my machine so I did it manually and now my server version 1.16.0.2 works perfectly!

I run my server on Windows 10 Enterprise on a LattePanda v1 with 4GB of RAM.

It's fixed! For anyone who has Windows 10 and has the same issue, I am not sure which Windows update fixed it, however, I removed the last 4 updates Windows did and re-installed them.

I had to download the updates directly from the Microsoft website myself, though if you can use Auto-Update do that instead to re-install. Windows Update had an issue running on my machine so I did it manually and now my server version 1.16.0.2 works perfectly!

I run my server on Windows 10 Enterprise on a LattePanda v1 with 4GB of RAM.

And Windows 10 2016 LTSB DOES meet system requirements and works perfectly after uninstalling the last 4 Windows updates and re-installing them manually from the Microsoft website.