Windows 10 event 78 seen in Zoom startup | Community
Skip to main content
Newcomer
May 2, 2022
Question

Windows 10 event 78 seen in Zoom startup

  • May 2, 2022
  • 1 reply
  • 2 views

I have the latest Zoom app on my Windows 10 21H2 level laptop. It works OK, BUT, I noticed that every time Zoom starts up, there is an event log entry, ID 78 (reproduced below). How do I report this to Zoom Support?

 

"Activation context generation failed for "C:\Users\tonyd\AppData\Roaming\Zoom\bin_00\Zoom.exe". Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_a8625c1886757984.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_60b5254171f9507e.manifest."

 

    1 reply

    td47Author
    Newcomer
    May 6, 2022

    FYI: I was unsure how many techies, or Zoom employees visit and view this forum for techical errors, so I decided to persevere and find how to raise a support ticket.  It took a bit of navigating, but I finally found the link: Hopefully this will help someone:

    From this support article:
    https://support.zoom.us/hc/en-us/articles/201362003-Zoom-technical-support

    See the link titled Web Ticket Request:

    https://support.zoom.us/hc/en-us/requests/new

    It seems that some technical issues can be resolved by downloading the "Cleanzoom.zip" file, unzipping and running the executable Cleanzoom.exe. Reboot, and then download the latest Zoom Meeting version.

    The cleanzoom.zip can be downloded here:

    https://support.zoom.us/hc/en-us/article_attachments/360084068792/CleanZoom.zip

     

    It seems possible from my reviewing the Windows Event 78 Log data, that some older updates (in-place upgrades or updater routines) where not cleaning up old (unused/unwanted) 32-bit code, so both X86 (32-bit) and amd64 (64-bit) routines were called incorrectly during startup, causing conflicts. The Cleanzoom.exe program semed to fix this up OK.