There is no update for this behavior. The behavior is a fundamental property of CRL-based OCSP server. In order to reduce the load, OCSP caches the referenced CRL for a period specified in CRL (Next Update) and revocation is not detected immediately. In revocation configuration provider settings you can specify how often OCSP should check for CRL updates:
do not set too small value, because OCSP can be overloaded with CRL download and update operations.
we can not change the version of our OS
interesting, why?