New
#11
Just an update. The problem has not (yet) reoccurred since I disabled the automatic startup of the Office 2000 component.
That should hex it nicely.
Just an update. The problem has not (yet) reoccurred since I disabled the automatic startup of the Office 2000 component.
That should hex it nicely.
Still fine,.so I will mark as solved. Thanks to everyone who offered advice.
It was too good to last! Just happened again, for first time in weeks. The Office 2000 component that seemed to have been causing the problem by being enabled at startup remains disabled so something else. Disabling clicktorunsvc on Task Manager did the trick (for now).
I looked at the Reliability History and saw that something called "Office Subscription Licensing Heartbeat" stopped wotrking just before noon today. Not sure what this is doing, given that I have Office 2019, not Office 365, therefore no subscription. The associated application is OLicenceHeartbeat.exe.
I have the same error since maybe last week.. Guess this will be repaired with the next Office update, also running of scripts is disabled now in all Office applications. This could be related to the last Exchange server vulnerabilities ...
Abour Office 2000 components, maybe it is time to check with autoruns what is starting and where
I almost fell off my chair at the thought that Microsoft might fix this! How many years have they had to do that?
FWIW, Autoruns showed the Microsoft Office 2000 Component still ticked under the Logon tab, even though I had disabled it on the Startup list in Task Manager. I have unticked it now. Autoruns also shows a number of other programs ticked even though (at exactly the same time) they are either shown as Disabled on Task Manager's Startup tab (OneDrive, the Steam Client Bootstrapper) or not visible there at all (the installers for Chrome and Edge).
It is fairly easy to circumvent, if annoying when you are in a rush. I suppose if it actually stopped you working Microsoft would have had to pay more attention to it.
Hi there
@thelordgiveth
glad you got it sorted -- but remember the extra bit (after your user name ) "and he taketh away " !!!! so take care !!!!
Cheers
jimbo
I think I adopted the user name as a reaction to my first broadband ISP, e7Even, who "gave" with a very cheap offer and then "took away" a few months later by landing me in a walled garden. Took ages to get a MAC (so back to dial-up for a bit) and even longer to get a refund.