Hello! Thank you so much for your inputs. But I am afraid I'd done that already. Well, after several twists and turns I discovered that this error was like an interplay between several updates this November, especially the Security Updates. I can pinpoint which specific Windows Update/s is/are the culprit of this problem. However I suspected that it was more on the Security Updates, I tried to disable/enable Windows Defender and by God's grace it worked. But every time I reboot my device I have to tweak the Windows Defender first before it can run smoothly. So for now I just have to pause my Windows Update until December hoping to get a permanent fix of this issue at that time. Please let me know if my solution is reliable or not. Thanks.
