Thanks for the help fg2001.
It is apparent that the fault is NOT patched in 22000.132 which is strange when you read what APPAULS has to say here.
So, it’s obviously worrying that a core element of Windows is giving the same error as a third-party file might, an element as crucial as security. Fortunately though, this issue is not prevalent on a large-scale as only a few users are reportedly facing this error. However, that number is still large enough that this has become a glaring issue that Microsoft will likely patch in the next update.
I looked for this problem in Fixes and Known Issues and was surprised by its omission.
Davy.