iadom

I have just checked and my version is (2407 Build 16.0.17830.20056) 32Bit. I will admit this PC is getting on in years now and will not update to Win11. Even so it is a 64 bit machine so I was surprised to find that I had a 32 bit version of Office installed. As the Office Apps now appear to be working correctly I am not going to go through uninstalling 32 bit Office 365 to install 64 bit Office 365. When this PC was new it had some dreadful McAfee software pre installed that took a very long time to get totally removed from my system but it also caused problems with Office installs. Even now every 5 or 6 months I have to go to the Control Panel and run the Office repair utility to get any Office Apps to run. I am used to doing it now so I will continue to live with it until this venerable piece of kit is replaced.

No, I had not altered any settings on Malwarebytes before this Word problem, it was only after searching for an answer to my problem that I came across your answer in the other thread I linked to that allowed me to fix it. I will check on my version of MS Word to see if it is up to date although I usually have auto update set on all App to be honest.

No, I was just trying to open the Word App to create a new, blank document. I tried from various sources, the full start menu, the quick start menu, the Microsoft 365 taskbar icon and eventually tried to open an old Word.doc from a few years back without success. Malwarebytes even ran an auto update whilst I was trying to fix the problem but that made no difference until I disabled Malicious return address detections.

I have not used the Word App for over a week and have just tried to use it. I was not opening an old file but trying to open the app for a new document. each time I tried Malwarebytes blocked it. I tried several of the suggestions in this thread It was only after I disabled 'Malicious return address detections' that I was able to get the Word App to open. As I was not attempting to open any existing files does this suggest the problem is with Malwarebytes and not any corrupt or suspect files on my PC? Malwarebytes Exploit Blocked Report 2024-08-25 151727.txt

Always have had that option ticked, in fact I'm sure I had a full update within the past couple of weeks, not sure why it was showing such an old version??

When I tried to run MB-Clean nothing happened at all. All very strange but it now appears to be fixed. My version of MB was up to date last week, always set to auto update. I have just run the latest copy from your link. After the download and clicking run, the installing dialog box came up but before any installation took place a warning popped up to tell me I must restart my PC to complete the install??? I did this and the normal install screen came up, clicked install and it went through perfectly, all appears to be OK ATM. All was fine before MS got there hands on it as I also had problems with my Acronis Backup app after they had finished but I was able to reinstall that to fix it. Many thanks for all your help. Jim.

Grr, tried to run FRST 64 but Smart Screen Defender blocked it. I do have a copy of an older version of FRST 10.4.2016.1 I was able to get that to run but it just produced two txt files, no zip, guess that is in the latest version? This is the best I can do. Addition.txt FRST.txt

dHmm, not good so far, the MB-Clean tool refused to run. Will give the diagnostics a try.

Many thanks for swift reply, I will get on it ASAP.

in a reversal of THIS thread I have exactly the opposite problem. Yesterday I tried to update Office 2013 to Office 365 but due to an error with the 'Click to run' service the install failed. I had to resort to Microsoft tech support who took remote control of my PC. They did eventually manage to install office 365 which is now running perfectly but I am left with another problem. On boot up I get an onscreen message to say that Malwarebytes is 'Unable to connect to the service'. If I try to run Malwarebytes I get the same message and I am unable uninstall or reinstall Malwarebytes. I contacted Microsoft support who didn't seem to accept it was something they had done, they suggested contacting Malwarebytes instead. Jim.