VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Richard, I did put up brand new, similar Windows 2019 server with 6 vCPU 's. And the newest release 9.16.20 starts there without problems, so this issue is really, like you addressed, with the vCPU count. I hope the bug will be corrected in the future releases, so the 8 vCPU Name Server

Re: [Question] About migration for 9.11.X to 9.16.X.

Hi, Thank you for replying. > called README. In it you will find the answers to your questions. Thanks. Yes, I know that. also, I wanted to hear from anyone who had actual experience and knowledge about migration as opinions. >You could also spend some quality time in the mailing list archives.

Re: [Question] About migration for 9.11.X to 9.16.X.

Hi there, On Thu, 19 Aug 2021, Techs-yama wrote: I'm thinking about BIND Version migration for 9.11.X to 9.16.X. Also, I'm about to check the different default config value and config parameters for the purpose of that now. I would like to ask you all. Are there any other points of observe

RE: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Sami, Could you try changing the number of vCPUs to either 6, 7, 9, or 10 and see if it then starts OK? If that works then you can either leave it like that or we can help you with a way to have BIND run a specific number of vCPU cores while you put the VM back to 8 vCPUs. Best, Richard.