Forum Discussion

PurSpyk's avatar
PurSpyk
Brass Contributor
Jul 16, 2022

Errors in Event Viewer

Since the latest beta update the following is appearing in Event Viewer:

 

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.15511.20000
P3: 0x8004323E
P4: New Document

 

Not too sure what is triggering this error, or which Office app is reporting it. 

windows
  • PurSpyk's avatar
    PurSpyk
    Brass Contributor
    Jul 27, 2022
    Latest beta build, 26 July 2022, still same error. How do we report issues that get noticed? Feeback hub is pointless, these forums are only users, feedback via Office seems to go unnoticed as well.
  • Lee_Martin's avatar
    Lee_Martin
    Copper Contributor
    Jul 19, 2022

    PurSpyk 

     

    I'm have that identical error on the July 2022 build of Windows 11.

     

    I have a 32-bit version of Office installed (because I need that version for a specific custom Access database).  Any chance you're running 32-bit Office?

     

    I also have iDrive automated backup software installed.  Launching a backup with that software seems to kill my Ethernet connection until I reboot.  Not sure if that's related.

     

    Do either of those two variables overlap with your situation?

    • PurSpyk's avatar
      PurSpyk
      Brass Contributor
      Jul 20, 2022
      Hi

      No I use the 64bit version and don't use idrive
  • Dan_Ross's avatar
    Dan_Ross
    Copper Contributor
    Jul 26, 2022
    I am finding the same error (and have a known Fast Flux DNS threat in my environment).

    Exploit Protection is killing a number of Office processes flagged for credentail stealing. I am not sure if they are related.
  • Deleted's avatar
    Deleted
    Jul 26, 2022

    same error here. on an insider build of windows 11 but not using the office "coming soon". wondering if that might address it.

    otherwise assuming its something that must be lived with until the fall update.

  • seanvree's avatar
    seanvree
    Copper Contributor
    Aug 04, 2022
    Same error for me:


    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.15427.20182
    P3: 0x8004323E
    P4: New Document
    • PurSpyk's avatar
      PurSpyk
      Brass Contributor
      Aug 06, 2022
      Latest version of Office, new Windows Updates, still same error reported. How do we get this fixed, feedback does not seem to be taken seriously
      • boing60's avatar
        boing60
        Copper Contributor
        Aug 07, 2022
        This happened in April and was eventually fixed....no it returns
  • Legion-Microsoft's avatar
    Legion-Microsoft
    Copper Contributor
    Sep 19, 2022
    Same here too. I used the Feedback-Hub and after a while I remark the restart of Windows File Explorer and checked directly my Event Viewer.

    At the same time the following error occurred in same second:

    Faulting application name: Explorer.EXE, version: 10.0.19041.2006, time stamp: 0x3e04d5ee
    Faulting module name: Windows.UI.Core.TextInput.dll, version: 10.0.19041.1806, time stamp: 0x7b0331de
    Exception code: 0xc0000005
    Fault offset: 0x000000000007b065
    Faulting process id: 0x1b00
    Faulting application start time: 0x01d8cc2820ab7720
    Faulting application path: C:\WINDOWS\Explorer.EXE
    Faulting module path: C:\Windows\System32\Windows.UI.Core.TextInput.dll
    Report Id: 94e23526-8364-42d7-9f3c-76b27f812ff3
    Faulting package full name:
    Faulting package-relative application ID:

Resources