[BDS-6333] Unable to start Created: 24/Jun/20  Updated: 24/Sep/20  Resolved: 27/Jun/20

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.16.0
Fix Version/s: None

Type: Bug
Reporter: qingqingni Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 1
Labels: None

Attachments: JPEG File -7bb963a595730ed9.jpg     File 20200626_120640.mp4     File 20200626_122035.mp4     JPEG File 28a4e12e54d8c951.jpg    
Issue Links:
Duplicate
is duplicated by BDS-6413 Dedicated Server No Start Error v1.16... Resolved
is duplicated by BDS-6434 How to fix my problem vps windows ser... Resolved
Confirmation Status: Unconfirmed

 Description   

The server fails to start, as follows.

When I use 1.14.60, there is no such problem.

Many people have reported that winsever2016 cannot be started.Someone has the same situation on windows10 ltsb 2016

Including your own computer or cloud server.

Because it used c++17 stl.



 Comments   
Comment by Sonata [ 04/Jul/20 ]

I test on a Windows Server 2016(1607&14383.1884),found it fail to run BDS.After install update(KB4103723[Log|https://support.microsoft.com/zh-cn/help/4103723/windows-10-update-kb4103723)] then it  work fine. So it is a feasible solutions. I also fount it work fine on Wine(5.0+). Thanks for your reply IonicEcko!

Comment by IonicEcko [ 27/Jun/20 ]

Thanks for letting us know Oscar.

Just to be clear though, Windows 10 2016 LTSB is not a supported operating system. Just because you were able to get it working now does not make it such.

Bedrock Dedicated Server is compatible with Windows 10 1709 and later operating systems. 2016 LTSB is based off the 1607 Windows image and therefore does not meet the minimum OS requirements.

Comment by Oscar Maldonado [ 27/Jun/20 ]

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.

Comment by Oscar Maldonado [ 27/Jun/20 ]

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.

Comment by qingqingni [ 27/Jun/20 ]

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

Comment by qingqingni [ 27/Jun/20 ]

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.

Comment by IonicEcko [ 27/Jun/20 ]

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

Comment by qingqingni [ 27/Jun/20 ]

BDS-6413 ,Windows 10 Enterprise 2016 LTSB

Comment by IonicEcko [ 27/Jun/20 ]

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

Comment by qingqingni [ 26/Jun/20 ]

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

Comment by Oscar Maldonado [ 26/Jun/20 ]

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

Comment by qingqingni [ 26/Jun/20 ]

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

Comment by Andres Martin [ 26/Jun/20 ]

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

Comment by qingqingni [ 26/Jun/20 ]

You can watch the video I uploaded.

One is 1.16.0, one is 1.16.0 compared with 1.14.60

Comment by qingqingni [ 25/Jun/20 ]

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.

Comment by Vitaliy Revenko [ 25/Jun/20 ]

LevelDB error could mean that your world files are corrupted

Comment by IonicEcko [ 25/Jun/20 ]

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.

Comment by qingqingni [ 25/Jun/20 ]

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

Comment by Sonata [ 25/Jun/20 ]

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

Comment by IonicEcko [ 25/Jun/20 ]

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.

Comment by qingqingni [ 25/Jun/20 ]

so terrible

Comment by Oscar Maldonado [ 25/Jun/20 ]

I am currently having the same issue on my Windows 10 machine.

Generated at Sat Jan 11 07:36:24 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.