Messages

Thanks Andrew. I just wish MS would leave things alone and stop making more work for us.

So happy I found this post as I've already spent so much time on WebView2. Unfortunately, according to this link, WV2 will no longer appear in the installed apps list.
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#announcement

WV2 has been such a pain for me, after provisioning/autopilot is complete and the user logs in, apps like Global Protect and Teams install. However, both Global Protect and Teams require WV2. Both apps fail because not being able to find WV2 although I can find WV2 in the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}

Has anyone else struggled with this and hopefully found a solution?

Thank you for the reply, I assume you mean the PC Feature and Application Request page?

Maybe I'm looking in the wrong place or it doesn't exist. I know about PatchMyPC-PublishingHistory.csv but it's lacking assignments along with availability. Does this information exist?

I'm also looking for an export of what applications I currently have configured in the publisher. As I deploy more applications it's hard to keep track of what I've configured and who I've deployed too.

If these don't exist, I'll be happy to submit and idea.

Thanks

Liviu,
I appreciate the response. I did just what you mentioned in the first bullet item and the app never showed up in Intune after the sync. I'll open a support ticket.

Thank you

The publisher worked properly and created MS Edge 112.0.1722.64 for Intune, but I noticed I failed to check the "disable auto update" option. I proceeded to delete MS Edge 112.0.1722.64 in Intune. I opened the publisher made the proper changes and checked "Republish during next sync schedule". I then clicked "Run Publishing Service Sync" and received notification "✅ Intune Application Updated: Microsoft Edge 112.0.1722.64 (x64)". However the application doesn't appear in Intune. Below is what I keep seeing after running the sync.
*** Report :       
A total of 0 updates were published with full content, 0 updates were published with Metadata only, 0 updates were revised, 0 updates were expired, 0 applications were published into ConfigMgr, 0 ConfigMgr packages were updated, 0 packages were revised, 0 ConfigMgr applications were auto-enabled, 0 updates were auto-enabled, 0 applications were published into Intune, 1 Intune application was updated, 0 Intune updates were published, 0 Intune updates were updated, 0 Intune applications were auto-enabled, 0 Intune updates were auto-enabled.   
*** Success:   
No update was published.   
No update was revised.   
No update was expired.   
No application was published into ConfigMgr.   
No package was updated into ConfigMgr.   
No package was revised into ConfigMgr.   
No ConfigMgr applications were auto-enabled.   
No updates were auto-enabled.   
No Intune applications were auto-enabled.   
No Intune updates were auto-enabled.   
No application was published into Intune.   
****** Intune Apps Updated:   
Microsoft Edge 112.0.1722.64 (x64) was updated into Intune   
No update was published into Intune.   
No Intune update was updated into Intune.   

I assume the issue is caused by me deleting the application from Intune, but how can I fix it? I did check the Intune Update for Microsoft Edge 112.0.1722.64 (x64) so I could continue the roll out.
Thank you

FabianSz you are a genius. You're 100% correct, after creating a new MST snag-it 23.1.0 installed properly.

Thank you for posting the fix!

Hi Spencer,
Thinking it was having a snag-it package issue, I deleted the app in Intune. I then have been having a heck of a time getting that package rebuilt. To recap, I had Snag-it 23.0.3 installed and then tried to run the full installer for 23.1.0 and it failed. I have uploaded the logs.

I too am having an issue. I had 23.0.3 installed and then pushed 23.1.0 to the device. I receive an Intune failure message and no snag-it installed. I'm currently going back and installing 23.0.3, grabbing the logs and then pushing 23.1.0 and grabbing the logs.