Hi Pritesh, it is a known post-update boot issue.
Since Safe Mode and repair tools fail, boot into Windows Recovery Environment, open Command Prompt, and run dism /image:C:\ /get-packages to identify the February KB, then remove it with dism /image:C:\ /remove-package /packageName:<KB>. If DISM removal is blocked, try wusa /uninstall /kb:<KB> /quiet /norestart. If rollback does not resolve it, the supported option is an in‑place upgrade repair using the Windows Server ISO, which preserves data and roles without formatting. This avoids a full rebuild while restoring system files to a working state.
I hope it's helpful, and if it is, please give it a thump up for accept the answer, very appreciate that!
Harry.