Windows update causes repeating Error in Office?

Topic

New Reply

For a number of users, recent updates to Windows cause a new error for Office, appearing frequently in Event Viewer.

The new error looks like this:

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15209.20000
P3: 0x8004323E
P4: New Document

This is being discussed on MS’s “Office Insider” at

https://techcommunity.microsoft.com/t5/office-insider/errors-in-event-viewer/m-p/3284603

Are you seeing the same thing?

 

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Replies

What version of Office?

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Susan – this continues to occur after April updates to Win 10 and most recent updates to MS 365 (f/k/a Office 365), on my two different Dell Optiplexes in two different locations.  On one of those Optiplexes, it’s happening maybe twice per day.

You will see the same persistence of this issue at the MS link I posted above at the start – that MS “Document” now has over 6,000 views.

Please send a note to your favorite MS Office contact and let us know what he says.

Thanks!

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Microsoft Office Home and Business 2016

Reply | Quote

Hey, Susan.  Mine is MS 365 Family, on two different PCs that show the same Errors in Event Viewer.

If you follow the link, you’ll see whatever versions info the others have supplied.  I think it’s the “P2” number.

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Getting this on 2 machines with MS 365 Apps for business. After updates today, I can’t seem to reproduce the issue

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

I am getting the error over and over with MS Office Home and Business 2019.

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Precisely which updates and on which operating systems?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

10 Pro. Noticed errors prior to applying april updates. Can’t reproduce after the updates were applied

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Well, checking logs this week an error is back

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

This is actually called a “Microsoft Office 16 Alert”, Event 300

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20218
P3: 0x8004323E
P4: New Document

Still getting this error over and over.

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

glnz wrote:

The new error looks like this: Failed to parse element: VersionOverrides Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null) P1: Apps for Office P2: 16.0.15209.20000 P3: 0x8004323E P4: New Document

I use MS Office Home & Business 2019 C2R on a Win 10 Pro v21H2 machine and I’m not seeing these errors.

I checked my Event Viewer today and discovered that I have almost 2,000 of these Event ID 300 “Microsoft Office 16 Alerts”, but they are only being logged as Information and aren’t the “Failed to parse element: VersionOverrides” errors being discussed in PurSpyk’s April 2022 thread Errors in Event Viewer in the MS Tech Community. My Information alerts date back to 20-Jan-2021, which is the same date that I updated from Win 10 Pro v1909 to v2004, but I’m not certain if that was the trigger or if older alerts have been purged from Event Viewer. All my alerts seem fairly innocuous – for example, the highlighted alert in my image below was logged today when I purged my Junk folder in MS Outlook 2019.

For anyone seeing the “Failed to parse element: VersionOverrides” errors, do you always see “P1: Apps for Office” as the first parameter and P4: New Document as the last parameter? In my case, my P1 parameter is always a 6-digit number (i.e., 300894 in my sample image but different for every logged event), P2 is my Office build (currently 16.0.15128.20178, rel. 26-Apr-2022) and my P3 and P4 parameters are always blank. I created a new document with MS Excel 2019 to see if that would generate an error but nothing was logged in the Event Viewer.
———–
64-bit Win 10 Pro v21H2 build 19044.1645 * Firefox v100.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.8.191-1.0.1666 * MS Office Home and Business 2019 (Version 2204 Build 15128.20178 Click-to-Run)
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

Reply | Quote

I am Win10/Pro 21H2 and I have Office 2019 Home and Student C2R. My last Office 2019 update was done on March 13 and after that I turned the Office update option OFF. It has been OFF ever since
(see attachment for the Office 2019 Product Information)

Installation of March Patch Tuesday patches:
….. CU and SSU on April 3.
….. .NET 5.0.15 on April 8.

Installation of April Patch Tuesday patches:
….. CU and SSU on May 2
….. .NET 3.5/4.8 on May 2
….. .NET 5.0.16 on May 2

I am getting the same Microsoft Office 2016 Alerts as @glnz and @mpw in the Event Viewer, #300, for my Office 2019.
The Error Level Alerts began on April 13, 9:53:22 PM. Like @glnz and @mpw’s posts, these Error Level Alerts are all “Failed to parse element: VersionOverRides” .
P1 is Apps for Office
P2 is 16.0.14931.20128 (which is what you get when you click on About Word {i.e., the blue box in the Product Information attachment}),
P3 is 0x8004323E
P4 is New Document.
(see attachment for Event Viewer 4-13-2022.JPG)

However, prior to April 13, the Event Viewer 300 Events were at the Information Level.
P1 is a code that corresponds to the type of information in the Word dialog box
P2 is 16.0.14931.20132 (which is what shows up at the bottom of the Product Information page {i.e, the red box in the Product Information attachment}).
P3 is empty
P4 is empty.
(see attachment for Event Viewer 4-11-2022.JPG)

These Error Level Alerts do not seem to be related to 2019 Office Updating, which was turned off long before these Error Level Alerts started occurring.
In addition, contrary to the reason stated in this topic heading, the first occurrence of these Error Level Alerts doesn’t coincide with the installation of the monthly CUs & SSUs, of the .NET 3.5/4.8 update, nor of the .NET 5.0.15 and .16 updates, either.

And the same thing is happening on my other laptop which has Office 2016 Home and Student C2R on it. Here again, the Error Level Alerts started on April 13, 9:46:49 PM. The 2016 Office update option was turned OFF long before, on March 21. March and April Tuesday Patches were installed on the same dates as on the other laptop that has Office 2019 on it, and the date on which these Error Level Alerts started on the Office 2016 laptop doesn’t coincide with the date on which the March or April Patches were installed on it.

Something else is triggering these Error Level alerts — it’s not Office Updates or Windows Updates.

Reply | Quote

WCHS wrote:

The Error Level Alerts began on April 13, 9:53:22 PM. Like @glnz and @mpw’s posts, these Error Level Alerts are all “Failed to parse element: VersionOverRides” . P1 is Apps for Office P2 is 16.0.14931.20128 (which is what you get when you click on About Word {i.e., the blue box in the Product Information attachment})

Hi WCHS:

It seems odd that your version of MS Office Home & Student 2019 C2R changed from 16.0.14931.20132 to 16.0.14931.20128 (a lower build number) on 13-Apr-2022.

Have you switched your MS Office Home & Student 2019 C2R installation from the Current Channel to a Monthly Enterprise or Semi-Annual Enterprise channel? Have you run a manual check for updates to see if a newer build is available for your installation?

My MS Office Home & Business 2019 C2R is on the Current Channel and received the latest Version 2204 Build 15128.20178 (rel. 26-Apr-2022) shown at Update History for Office 2016 C2R and Office 2019 for retail versions of Office 2019.  If I go to File | Office Account | Office Updates | Update Options | Update Now the manual update check reports there are no available updates for my Office installation.

I can’t find any information about your exact build 14931.20128 on the Microsoft site but the Microsoft 365 chart <here> currently shows that the Monthly Enterprise Channel and Semi-Annual Enterprise Channel (Preview) both should have received Version 2202 Build 14931.20274 on or around 12-Apr-2022.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1645 * MS Office Home and Business 2019 (Version 2204 Build 15128.20178 Click-to-Run)

Reply | Quote

Hi @Imacri,
There has been a long discussion about the difference in the build number at the bottom of the File | Account page and the build number in the dialog box when clicking on the “About Word” icon also at the bottom of the page. I made a post – #2434807 about this difference, which is among the Comments to the AskWoody-Newsletter-Plus-(Issue-19.13 2022-03-28) article with the title “License and Registration, Please” by Peter Deegan. The comments to the article are here.

My post #2434807 was about the mis-match in build numbers in 32-bit Word 2016 on my 7569 laptop in those two places:
a) At the bottom of the page under the heading “About Word”: Here I have 16.0.14931.20132 (it is still this version because I have Word updates turned off). This build number comes from C:|Program Files (x86)| Microsoft Office | root | Office16 | WINWORD.EXE.
b) After clicking on the About Word icon: Here the dialog box says 16.0.14931.20118 (released sometime around Feb 28, as one of the screenshots in #2434807 indicates). It was said in the aforementioned discussion that this build number comes from WWLIB.DLL, but my WWLIB.DLL is version 16.0.14931.20128, and not .20118. Deegan’s answer to this is that sometimes the build number in the dialog box comes from Office as a whole and not from WWWLIB.DLL. I later discovered that this build number in the dialog box comes from csi.dll (Microsoft Office Document Cache).

How did I discover this? I checked this all out on the File |Account page in my other laptop (model 5482), which runs 64-bit Word 2019, which is one you are asking about.
a) Similar to the 7569, at the bottom of the page under the heading “About Word”, I still have 16.0.14931.20132. This build number comes from C:| Program Files | Microsoft Office | root | Office16 | WINWORD.EXE. [not Program Files (x86), since 2019 Word is 64-bit
b) After clicking on the About Word icon, tbe dialog box says 16.0.14931.20128 (which you can see in my screenshot at post #2434807 and still is that version now). On this 5482 laptop, WWLIB.DLL is version 16.0.14931.20128, which did/does match the version in the dialog box. So, I asked myself what other .dll or .DLL files on the two machines have a version/build number that matches the build number in the dialog box?. The only .dll/.DLL file where its version number matches the build in the dialog box on the two machines is the csi.dll file. So, that’s how I conclude that the build number in the dialog box doesn’t come from WWWLIB.DLL, but instead comes from csi.dll.

So, in answer to your comment, the build number in the dialog box didn’t change from .20132 to .20128. It has been .20128 for a long time on the 5482, just as it’s been .20118 for a long time on the 7569. This is because the version/build info in the dialog box doesn’t come from WINWORD.EXE (as it does at the bottom of the File | Account page), but instead comes from a .dll file (I say it comes from csi.dll, but others have said it comes from WWWLIB.DLL).

I will update both 2016 and 2019 Word and report back as to what is at the bottom of File | Account page and in the About Word dialog box afterwards.

Reply | Quote

Hi WCHS:

Sorry, I missed the comment in your post # 2444250 that “My last Office 2019 update was done on March 13 and after that I turned the Office update option OFF.” I had assumed you found a way to change your MS Office Home & Student 2019 C2R from the default Current channel to the Semi-Annual channel (I noticed you had posted in Susan Bradley’s Tasks for the Weekend – April 10, 2021 – Change Your Office), but if you are still on the Current channel and have automatic updates disabled at File | Office Account | Office Updates | Update Options | Disable Updates then that explains why your MS Office Home & Student 2019 C2R is still on Version 2202 Build 14931.xxxxx.

It will be interesting to see if your “Failed to parse element: VersionOverrides” errors (Event ID 300) disappear from the Event Viewer once your MS Office products are updated to the latest Version 2204 Build 15128.20178 for Current channel users.
—————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1645 * MS Office Home and Business 2019 (Version 2204 Build 15128.20178 Click-to-Run)

Reply | Quote

I have latest update and still getting Microsoft Office 16 Alerts . Here is the whole thing.

Log Name: OAlerts
Source: Microsoft Office 16 Alerts
Date: 5/5/2022 3:22:43 PM
Event ID: 300
Task Category: None
Level: Error
Keywords: Classic
User: PC-WIN10\mpw
Computer: PC-Win10
Description:
Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15128.20158
P3: 0x8004323E
P4: New Document

Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Microsoft Office 16 Alerts” />
<EventID Qualifiers=”0″>300</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2022-05-05T20:22:43.6787992Z” />
<EventRecordID>69</EventRecordID>
<Correlation />
<Execution ProcessID=”0″ ThreadID=”0″ />
<Channel>OAlerts</Channel>
<Computer>PC-Win10</Computer>
<Security UserID=”S-1-5-21-970280769-3728618077-987578801-1002″ />
</System>
<EventData>
<Data>Failed to parse element: VersionOverrides
</Data>
<Data>Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
</Data>
<Data>Apps for Office
</Data>
<Data>16.0.15128.20158
</Data>
<Data>0x8004323E
</Data>
<Data>New Document
</Data>
</EventData>
</Event>

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

1 user thanked author for this post.

WCHS

Reply | Quote

mpw wrote:

I have latest update and still getting Microsoft Office 16 Alerts . Here is the whole thing.

I am Win 10/Pro 21H2 Build 19044.1645
I’d like to add a similar comment as that of @mpw’s post partially quoted here.

I am still getting the Microsoft Office 16 Alerts, too, after updating to the most recently available Retail Version of Mcrosoft Office Home and Student 2016 C2R, Version 2204 (Build 15128.20178), released April 26, 2022. See the Office 2016 version/release history here.

This new update Version 2204 Build 15128.20178 is indicated at the bottom of the File | Account page, as shown in the attached “Office Product Information.JPG. {NOTE: I turned Updates OFF after the update.} This version/build info is the same as that of WINWORD.EXE.

However, as shown in the Office Product Information attachment, the “About Word” icon brings up a dialog box which says that version/build is Version 2204 Build 15128.20128 and that is the version/build indicated in the event viewer’s Event Properties – Event 300 listed in the screenshot below.

{Note: I have yet to figure out what file provides this version/build info in the dialog box. I thought it was from the csi.dll, when I was investigating this issue after the the prior update version was installed. This is because the version/build of the csi.file was the only one that matched the version/build of the info in the dialog box. But, now that I have updated to .20178, the version/build of the csi.dll file (Version 2204 Build 15128.20112 ) does not match the build/version in the dialog box (Version 2204 Build 15128.20128).

As a matter of fact, I can find no file at C:|Program Files (x86)|Microsoft Office|root|Office16 whose version/build info matches that of the dialog box. I still don’t know where the info in the “About Word” dialog box comes from, but it is the same info as that of 16.0.15128.20128 for P2 in the screenshot. (It is NOT the same info as that at the bottom of the File|Account page — 15128.20178)
}

Here are the details of the Microsoft Office 16 Alert, Event 300:

I wish I could report it in the same format as the one used by @mpw, but I don’t know how to find the log (I assume it is in a log that is located somewhere on my laptop). The same info is in the screenshot, though.

Reply | Quote

Hi @mpw,

mpw wrote:

Log Name: OAlerts
Source: Microsoft Office 16 Alerts
…

Is this in a logfile? If so, where is it?

Reply | Quote

Computer Management>Event Viewer>Overview and Summary>Summary of Administrator Events>Error

Right click and choose “View all instances of this error”

 

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

1 user thanked author for this post.

WCHS

Reply | Quote

I had already gotten that far (following a different path) as you can see in the Office-16-Alerts-Event-300.jpg attachment in my my post – #2444675 .

But, after your answer, I clicked on the ‘copy’ button (I had cut that off in the screenshot), and the contents on the clipboard are in the format in which you posted.

Thanks for the tip.

Happy to see in @Imacri’s post that Microsoft has the problem under investigation!

Reply | Quote

Does the “new error” have any impact on the operation of Microsoft Office?

Reply | Quote

Kathy Stevens wrote:

Does the “new error” have any impact on the operation of Microsoft Office?

Doesn’t seem to. But, it generates a lot of #300 events – one for every new document you open.

Reply | Quote

I do not notice any problem.  Mostly use Office Outlook 2019 and it shows no problems.

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

Reply | Quote

BrReich-MSFT posted in the MS Tech Community thread Errors in Event Viewer on 04-May-2022 that these “Failed to parse element: VersionOverrides” errors being logged in the Event Viewer are being actively investigated by Microsoft and that a bug was officially filed on 03-May-2022.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1645 * MS Office Home and Business 2019 (Version 2204 Build 15128.20178 Click-to-Run)

3 users thanked author for this post.

WCHS, mpw, windbg

Reply | Quote

These errors just started again following July patches

1 user thanked author for this post.

appyface

Reply | Quote

Getting a slightly different message over and over, thousands in a day:

Failed to parse element: Requirements
Id=87b35109-b1d7-4cdf-9cbb-84c1d946d22b, DisplayName=CV Surveys Win32, Provider=Amplify Signals and Insights Team, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15330.20260
P3: 0x8004323E
P4: New Document

Surface Pro 3 (long in the tooth but still going), did a Win10 Pro 21H2 refresh (keep user data), followed by local file (re) install of Office Professional Plus 2016 (click-to-run). Office updated shortly after.

I have been running this version of Office since getting the Surface and through all of the Win10 iterations and a few Win10 refreshes, and have never gotten any event messages like this until now.

Reply | Quote

OK, I did a refresh (keeping user data) of Win10 Pro 21H2 again yesterday. I also uninstalled every office related app that came with Win10 – Office 365, OneDrive for Business, Skype for Business, Outlook, etc. I did not install my copy of Office 2016 Professional Plus or any other office app.

This morning I have two event log entries same as I reported above. So doesn’t seem to be related to install of Office 2016 PP.

Reply | Quote

appyface wrote:

Getting a slightly different message over and over, thousands in a day: Failed to parse element: Requirements Id=87b35109-b1d7-4cdf-9cbb-84c1d946d22b, DisplayName=CV Surveys Win32, Provider=Amplify Signals and Insights Team, StoreType=SdxRdx, StoreId=(null) P1: Apps for Office P2: 16.0.15330.20260 P3: 0x8004323E P4: New Document

Hi appyface:

You might find some helpful information about your specific “Failed to parse element: Requirements” error in PurSpyk’d 16-Jul-2022 thread Errors in Event Viewer in the Office 365 | Office Insiders board of the MS Tech Community.  As you noted, your error is slightly different than the “Failed to parse element: VersionOverrides” error reported by glnz in this thread.

I checked my Event Viewer today and I don’t see either of these errors logged for my 64-bit MS Office 2019 Home and Business.  The good new for glnz is that a bug fix appears to be in the works for their “Failed to parse element: VersionOverrides” error (see post # 2444704).
—————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1826 * Firefox v102.0.1 * Microsoft Defender v4.18.2205.7-1.1.19400.3 * Malwarebytes Premium v4.5.11.202-1.0.1716 * Macrium Reflect Free v8.0.6867 * MS Office 2019 Home and Business Version 2206 (Build 15330.20264 Click-to-Run)

Reply | Quote

Thank you for your reply. I’m not seeing any help in the thread you linked from PurSpyk, though? What are you seeing in there, that I should take a look at?

 

Reply | Quote

Hi appyface:

I would suggest you post in that Errors in Event Viewer thread and that providing your system details (e.g., your computer model, the exact version and build of your Windows OS and Office 2016 Professional Plus, when your problem started, etc.).  It might help other users posting there to narrow down the root cause (I have no idea what the error “Failed to parse element: Requirements” means but perhaps a recent MS Office 2016 update is now having issues determining if your Surface Pro 3 meets the minimum system requirements) and the more users that report the issue in that MS Tech Community thread the more likely that BrReich-MSFT or one of the other Microsoft employees monitoring that forum will take notice.
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1826 * Firefox v102.0.1 * Microsoft Defender v4.18.2205.7-1.1.19400.3 * Malwarebytes Premium v4.5.11.202-1.0.1716 * Macrium Reflect Free v8.0.6867 * MS Office 2019 Home and Business Version 2206 (Build 15330.20264 Click-to-Run)

Reply | Quote

All of these 2016 Office Alerts (Event #300 – Error) [both the old ones and the new ones] seem to be associated with opening a new document. See the blue square in the attached screenshots.]

For me, the old ones in glnz’s post #2440527 on April 19 stopped on May 6, 3:37:07 PM (after occurring every day from April 13 to May 6). Note the ID information in the red square in the attachment for those old ones.

Now, like @appyface, I am getting these new ones. They started on July 15, even before I updated 2016 Office on July 20, and have been occurring every day since. Note the ID information for these new ones in the red square in the attachment for the new ones. The ID information now is the same as those for @appyface and different from the old ID information.

I am seeing the exact same thing for my Office 2019 Alerts (Event #300 – Error) on another machine.

To address Tony Stone’s post $2462847 on July 18, it doesn’t appear that the emergence of this new Alert coincides with a WU Patch Tuesday update (since the new Alert emerged on July 15 and I had done the June WU patch about 2 weeks before that — on July 3. And I haven’t applied the July WU patch yet, so the July WU could not be a factor here).

In addition, it doesn’t appear that the emergence of this new Alert coincides with updating Office either (since the new Alert first emerged on July 15 {and has appeared every day after that} and I didn’t update Office until July 20. (I always update Office manually and turn ‘updates’ OFF afterwards.)

Unless there’s some lag time going on …

1 user thanked author for this post.

appyface

Reply | Quote

We are seeing the same Provider=Amplify Signals and Insights Team error for Win10Pro users with 365 Office. Random app shutdowns or no startups or freezes.

Reply | Quote

Thanks, I haven’t installed Office since this last refresh of Win10 Pro last night, so I don’t think that thread will help me?

I am thinking the errors are coming from whatever comes with the Win10 Pro refresh – looks like free/trial version of Office 365… I found this page: https://support.microsoft.com/en-us/office/uninstall-office-from-a-pc-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8 and used the Powershell method to remove Office 365. Will wait several hours today and see what happens. The errors were coming every 4-5 hours in the event log without the refreshed PC being used at all.

Reply | Quote

My Office editions are Office Home and Student 2016 (Retail, C2R) on one machine and Office Home and Student 2019 (Retail, C2R) on another machine. No Office 365 here–not even a free/trial version.

Reply | Quote

So, after using the powershell removal method on the “delivered by Win10 Pro refresh” Office 365, I decided to also download and install/run the Office Cleanup tool (from that same link I gave above) for grins.

I’m glad I did. It installs as the “Microsoft Support and Recovery Assistant” with many options besides Office. I directed the tool to remove all office versions it finds without any reinstall assistance. The tool found remnants of Office 2010 and Office 2007, neither of which I have ever owned and certainly not ever installed (by me) on this machine, of which I am the original owner. Anyhow after rebooting and waiting all day, I have -0- Office alerts in the event viewer.

I need my Office installation back so now I am going to install Office 2016 Professional Plus and see what happens next.

Reply | Quote

The same events are back following the install of Office 2016 Professional Plus. BTW, my Office install is 32-bit, in case that matters.

1 user thanked author for this post.

WCHS

Reply | Quote

Hi @appyface:
Others are seeing this issue, too. The last time this problem occurred (i.e., the one @glnz reported), it started appearing April 13 and was fixed on May 6. Have you reported it, as @Imacri suggests here?

Reply | Quote

I had the previous parse error from mid-April until May 6.  It did not seem to have any effect on my computer or Office Outlook 2019.

I have Microsoft Office Home and Business 2019 mainly because I use Office Outlook for mail.  And sometimes word.  I don’t use Excel or PowerPoint.

I just installed July, 2022 updates for Windows 10 and Office 2019 (CTR) updates.  The error has not appeared.  If it does, I will post.

HP Pavilion Desktop TP01-0050 – 64 bit
Windows 10 Home Version 22H2
OS build 19045.5608
Windows Defender and Windows Firewall
Microsoft Office Home and Business 2019
-Version 2502(Build 18526.20168 C2R)

1 user thanked author for this post.

WCHS

Reply | Quote

The new Beta version of Office and Windows 11, and the errors are still present. Odd for a few months the errors no longer appeared, and I assumed it was a version of Office that caused this. If it’s bad Windows updates, then it affects both Windows 10 and 11.

Reply | Quote

Yes a repeat of the April events which MS says they investigated and fixed

Reply | Quote

Happening frequently on four different PCs in two different locations.

Reply | Quote