J
Jolvos
Guest
I've been finding this for years, from Windows 7 (and who knows if before) to Windows 10, from out of the box PCs to others with a clean disc format, but nearly the 50% of the PCs end up with this in the Event Viewer.
I've heard that's due to Office errors, hardware vendor faulty drivers and whatever, and the solutions proposed ("setup.etl" and so) never work for more than 48 hours.
Microsoft Staff at forums continuously give either canned or contradictory responses, and the Event Viewer text is cryptic as hell, so...
FOR THE LOVE OF GOD, WHEN ARE YOU EITHER SOLVING IT OR, IF THAT'S NOT A MICROSOFT ERROR, AT LEAST, CLARIFYING WHAT IS IT FOR EVERYONE TO KNOW IT?
I'm sorry for the tone and the caps, but I'm sick tired of, whenever I have to solve anything, having to dive in an ocean of non-event events, real errors and fake errors. And I can accept mistakes, but I can't accept the passivity of ignoring an issue during nearly a decade.
/rant
More...
I've heard that's due to Office errors, hardware vendor faulty drivers and whatever, and the solutions proposed ("setup.etl" and so) never work for more than 48 hours.
Microsoft Staff at forums continuously give either canned or contradictory responses, and the Event Viewer text is cryptic as hell, so...
FOR THE LOVE OF GOD, WHEN ARE YOU EITHER SOLVING IT OR, IF THAT'S NOT A MICROSOFT ERROR, AT LEAST, CLARIFYING WHAT IS IT FOR EVERYONE TO KNOW IT?
I'm sorry for the tone and the caps, but I'm sick tired of, whenever I have to solve anything, having to dive in an ocean of non-event events, real errors and fake errors. And I can accept mistakes, but I can't accept the passivity of ignoring an issue during nearly a decade.
/rant
More...