I think that so far we are simply stuck with the procedure Microsoft Support Engineers have to follow. And I believe there is the following assumption at Microsoft:
1. The problem can't be with Windows 8.1 Update as it was tested internally before release.
2. The problem must have been covered by existing KB articles and Fix-Its.
3. The problem is not critical - it does not contribute to data loss or poses a security threat.
- It's unknown how widespread the problem is (it's not a crash so the error is not sent out to Microsoft automatically, I guess).
Personally, I'm willing to go through the entire process with Microsoft Support just to confirm if it's a Windows 8.1 Update issue (I would guess it is). And afterwards, if the issue is not widespread, it probably won't be fixed as the cost of the whole
process of fixing the problem will outweight the potential gain.
If the issue is widespread though then there is a chance for a fix (probably a silent one - with a Windows Store update for example)