For a few days Microsoft users have been complaining about a series of problems related to sending e-mails through Outlook: it is good to know, at least for those who use the “classic” version of the program, which it is a decidedly widespread malfunction.
Apparently the Redmond giant is aware of the situation and is already trying to resolve the bugwhich expects to be able to leave behind with a fix on the short launch ramp available to everyone. While waiting for the malfunction to be solved, the only possibility that Outlook users have is to make a downgrade compared to the version of the app in which the problems with emails have been recorded. Of course, this is not the definitive solution, but in this way you can continue to use the program waiting for the official Fix.
The classic version of Outlook affected by the anomaly is the 2412, Build 18324.20168: those who have made this update complain in fact a block of the application when you try to write a new email, to respond to someone or to forward an e -mail message. In essence, the malfunction occurs whenever the writing interface of a message is opened.
As suggested by Microsoft, it is possible to check if the problem is precisely the one described simply by starting the Windows Event Viewer Application Log And looking for the anomalous arrest called “Event 1000” or “Event 1001” with these details:
Faulting Application Name: Outlook.exe, Version: 16.0.18324.20168, Time Stamp: 0x677828da
Faulting Module Name: Outlook.exe, Version: 16.0.18324.20168, Time Stamp: 0x677828da
Exception Code: 0xc0000005
Fault Offset: 0x0000000001A7C02A
FAULTING PROCESS ID: 0x0xfd0
Failing Application Start Time: 0x0x1db65d0fd0b9857
Faulting Application Path: C: Program Files Microsoft Office Root Office16 Outlook.exe
Faulting Module Path: C: Program Files Microsoft Office Root Office16 Outlook.exe.
Bosogna is necessarily waiting for the Fix To continue using the app? Fortunately, the company indicated a method to temporarily circumvent the problem before January 28, the date in which Microsoft counts
to release the “501 Build 18429,20000” update.
In fact, it is possible to carry out a downgrade to a previous version, such as 2411 (Build 18227.20162) following a few simple steps:
- open the command prompt from an administrator account;
- Copy and paste the two following commands and press send after each of them: 1) “CD %Programfiles % Common Files Microsoft Shared Clicttorun”, 2) “Officec2rclient.exe /Update User Updatetoversion = 16.0.18227.20162”;
- Disable updates from: File> Account Office> Update options> Disable updates. The goal of this change is to prevent Outlook once again installs the most recent version, namely the one with the bug;
- Finally, set the date of 11 February in a reminder to remember to reactivate automatic updates in time.