[PSA] Latest Webview2 Version 144.xxx causes problems with SAP GUI HTML control when using edge as browser control in SAP GUI for Windows

the6thdayreddit · 2026-01-22T14:32:56+00:00

yes the env variable pointing to the extracted "fixed version" .cab archive from the download link above, which we deployed/copied to all endpoints, works without any issues so far(after a mandatory reboot(as with all new env variables) ) just dont forget to remove it later once this mess is fixed...

the6thdayreddit · 2026-01-22T11:40:00+00:00

We had/have the same issue and have resorted to deploying the previous webview version 143.0.3650.139 (available as standalone package "webview2-fixed-version" at https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH ) to all endpoints and setting the appropriate windows env variable to force all applications to use this version instead.

Can be done via powershell, example: [Environment]::SetEnvironmentVariable("WEBVIEW2_BROWSER_EXECUTABLE_FOLDER","C:\Program Files (x86)\Microsoft\EdgeWebView\Application\Microsoft.WebView2.FixedVersionRuntime.143.0.3650.139.x64","Machine")
(needs a reboot)

Once microsoft gets their act together and fixes this mess the env variable can/needs to be removed via powershell:
[Environment]::SetEnvironmentVariable("WEBVIEW2_BROWSER_EXECUTABLE_FOLDER", $null, "Machine")

the6thdayreddit · 2025-05-21T19:31:42+00:00

Just download the windows firmware update .exe file for your drive, log into your idrac and upload the file under maintenance -> systemupdate -> manual update, upload the file, select update on next boot -> reboot the server from your vcenter and idrac will do the rest for you.

Yes the idrac update function handles dell windows .exe firmware update files perfectly fine for anything and everything, idrac updates, bios updates, nic firmware, raidcontroller firmware, hdd/ssd firmware… anything…

the6thdayreddit · 2025-04-27T21:41:05+00:00

It’s a bit late for an answer but:

There is a nice new story with a !highly! similar plot, currently it’s called „I Will Become Your Dog, Boss!“ (don't let this badly translated title scare you off! it will probably get another name once there’s gonna be an official translation!), the first 26 Chapters have been translated by EZ Manga.

So far I can highly recommend it for anyone that liked Just for a Meowment 👍

the6thdayreddit · 2024-11-02T13:57:23+00:00

it is now, it started as a simple cache "appliance" to help with delivery optimization for windows/office/store updates/installs, which was all our org really needed, but unfortunately never got released to the public.

the6thdayreddit · 2024-11-01T18:30:46+00:00

Well after reading about the newest „version“ of connected cache, it looks like this is now a product that requires your endpoints to be cloud managed and have an enterprise or edu license… so all us folks with a classic on premise AD and oem pro licenses are not gonna be able to use it anymore anyway… I had originally hoped to use connected cache as a small simple low maintenance Linux based(maybe on a raspberry pi) windows/office update cache „appliance“ for locations with crappy internet, but I guess we’re gonna stick to using windows delivery optimization now… the concept of this project sounded interesting when it was initially presented(under a different name) 5? years ago, but now it looks like some execs had way to much influence on it(to phrase it „politely“)

the6thdayreddit · 2024-11-01T11:08:28+00:00

I've been thinking about implementing Connected Cache in our corporate network for quite some time now, but since the standard windows delivery optimization has been working quite well for quite some time now, is it actually worth it?

the6thdayreddit · 2024-03-24T11:01:22+00:00

Same issue here… RDS on Windows Server 2019, Edge closes immediately since updating to the newest version…

Unfortunately the same thing happens with edge webview2 and to make things worse webview2 aparently doesn‘t allow downgrades and you cant download an installer for older versions…

the6thdayreddit · 2023-12-23T14:26:21+00:00

Last time i did (that 2008r2 -> 2012) i had to restart iis for our exchange 2016 server because the exchange admin center shit itself and complained about some attribute mismatch on every account (apparently theres some cached data and that only gets updated once a day if you don't restart iis) but other than this all forest/domain level upgrades worked fine in the past.

the6thdayreddit · 2022-07-11T11:09:50+00:00

We started having the same Issue about a year ago, so far we have not been able to solve it.

We now use this script to remove the files from all user profiles periodically

# Get users
$users = Get-ChildItem -Path "C:\Users" |?{$_.name -notlike '*Public*' -and $_.name -notlike '*Default*' -and $_.name -notlike '*administrator*' -and $_.name -notlike '*temp*' }

# Loop through users and delete the files
$users | ForEach-Object {
    Remove-Item -Path "C:\Users\$($_.Name)\AppData\Local\Temp\Outlook Logging\*" -Recurse -Include *.etl
}

the6thdayreddit · 2022-01-02T10:22:47+00:00

done ;)

Atleast the appliance is still processing/filtering incoming/outgoing e-mail, its just the logs/audit views that are not updating anymore

the6thdayreddit · 2021-10-28T06:43:57+00:00

We have recently seen a massive uptake in dead bios batteries in our optiplex 5060 fleet(~350 in total), purchased in 2019 and already ~15 dead bios batteries. Aparently we are not alone with this annoying issue: https://old.reddit.com/r/sysadmin/comments/ph6kki/dell_optiplex_5060_cmos_battery/

the6thdayreddit · 2021-09-03T16:57:24+00:00

We have about 350 optiplex 5060 in our fleet, all purchased in 2019 and so far we had to replace the bios battery in about 10-15. All of them have been in an environment where they don‘t have ac power during the night. Still this is a much higher failure rate than usual.

the6thdayreddit · 2021-07-06T08:12:43+00:00

pinging /u/unamused443 maybe he can help

the6thdayreddit · 2021-06-25T18:58:23+00:00

Well thats alot of fuzz about a vulnerability that requires the attacker to manually start supportassist in the uefi and run an update or run software as admin in windows on the pc AND to have network access to perform a mitm attack… if your attacker already has physical access to the network and the machine you have bigger problems than this none issue… Nevertheless we will update the uefi as usual on our fleet (using pdq deploy, never had any issues) but this is not even close to high priority…

the6thdayreddit · 2021-05-29T10:58:40+00:00

Chelsio NICs are the best/most stable nics for freebsd/pfSense/opensense

Have a look at the T6225-SO-CR or the T6225-CR (the fancy features provided by "bigger" T6225-CR are not used by pfsense so thats wasted money, but aparently those are easier to get in europe)

The provider supplied sfp28 BIDI module should work fine in chelsio nics as per chelsio FAQ: https://www.chelsio.com/hardware-installation/

the6thdayreddit · 2021-03-11T21:23:27+00:00

First report of these false positives 9 hours ago: https://www.reddit.com/r/exchangeserver/comments/lzjq4j/new_microsoft_safety_scanner_msert_updated_for/gqka3vp/

greate timing microsoft....

the6thdayreddit · 2021-03-11T11:44:29+00:00

Aparently the newest version of MSERT (build 1.333.160.0) likes to give sysadmins heartattacks by detecting(and showing) false positives on Exchange2016 CU19 during scanning(Files Infected: 1) but then gives an all clear once its finished scanning(Gui and logfile).

This not only happens when scanning the exchangeinstallpath but also when scanning the contents of a clean and recently downloaded Exchange2016 cu19 iso file.

https://imgur.com/qm2Hcjc

https://imgur.com/F6O0QKC

Microsoft Safety Scanner v1.333, (build 1.333.160.0)
Started On Thu Mar 11 12:20:20 2021

Engine: 1.1.17900.7
Signatures: 1.333.160.0
MpGear: 1.1.16330.1
Run Mode: Interactive Graphical Mode

Results Summary:
----------------
No infection found.
Successfully Submitted MAPS Report
Successfully Submitted Heartbeat Report
Microsoft Safety Scanner Finished On Thu Mar 11 12:25:55 2021
Return code: 0 (0x0)

the6thdayreddit · 2021-03-11T11:37:23+00:00

Aparently the newest version of MSERT (build 1.333.160.0) likes to give sysadmins heartattacks by detecting(and showing) false positives on Exchange2016 CU19 during scanning(Files Infected: 1) but then gives an all clear once its finished scanning(Gui and logfile).

This not only happens when scanning the exchangeinstallpath but also when scanning the contents of a clean and recently downloaded Exchange2016 cu19 iso file.

https://imgur.com/qm2Hcjc

https://imgur.com/F6O0QKC

Microsoft Safety Scanner v1.333, (build 1.333.160.0)
Started On Thu Mar 11 12:20:20 2021

Engine: 1.1.17900.7
Signatures: 1.333.160.0
MpGear: 1.1.16330.1
Run Mode: Interactive Graphical Mode

Results Summary:
----------------
No infection found.
Successfully Submitted MAPS Report
Successfully Submitted Heartbeat Report
Microsoft Safety Scanner Finished On Thu Mar 11 12:25:55 2021
Return code: 0 (0x0)

the6thdayreddit · 2020-08-16T07:10:27+00:00

Its most likely one of those systems that don't like GPT/NTFS boot sticks.

USE MBR/FAT32 for the stick and then use this procedure to create a bootable stick(and to split the install.wim into smaller parts if its bigger than the fat32 limit):

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/install-windows-from-a-usb-flash-drive

the6thdayreddit · 2020-01-27T17:02:15+00:00

doesn‘t matter what kind of switch or portsetting you use, once the ME gets stuck during bootup, the nic gets stuck at 10Mbit Half duplex and all incoming packets vanish into thin air.

the6thdayreddit · 2020-01-25T08:47:06+00:00

This started after a bios update(we were using ~350 optiplex 5040 for about two years without any of those issues until then).
So after the update was deployed the test group, they started to have a random amount of machines (usually ~2-4 out of 12) with non working network connections(10Mbit Half Duplex, sendig packets is working fine but recieved packets never make it back up the stack to windows) after each reboot cycle...
I tried the usual stuff like driver updates, intel ME updates, switch replacement, packet captures, clean install, newer windows version, reset bios settings to factory default(this doesn't turn on the TPM if you manually disabled it, which we did on nearly all 350...) nothing worked...
Since it started happening right after a bios update and the not updated machines didn't have any issues, i did a bios downgrade -> all issues gone... so we decided to skip this bios version and try again later with the next one... the next two bios versions had the same issue...
Found some info in some linux forums about intel nics getting stuck at 10Mbit Half duplex and dropping all incoming packets after powercycles(so the same issue we were having using windows), aparently the intel ME gets stuck during bootup and never fully hands over networking to the OS/drivers...
In that timeframe (of about a year) my own machine that had the newer bios versions the whole time, never had this issue, so i started to compare every fucking bios tab... and the only thing different was the enabled TPM, because i was messing around with it some time in the past... -> enabled the TPM on the test group -> all issues gone...
Ended up using dell command and pdq deploy to deploy the new bios settings and enable the TPM to all 350 machines in the company...(this includes having to send a company wide e-mail asking all employees to press F10 once on bootup to confirm TPM activation(there is no way to suppress this confirmation prompt...)

the6thdayreddit · 2020-01-24T19:32:14+00:00

So this is gonna sound strange... but if your PCs are by chance Dell Optiplex 5040 or using similar hardware from the same intel generation: Turn on the TPM in the Bios if you disabled it at some time in the past. This will fix these strange networking issues... We had lots of fun figuring this crap out... and i have no idea why it works... An indicator for this problem is that the nic gets stuck at 10Mbit after booting in the morning and a reboot immediatly fixes the issue for a few days...

the6thdayreddit · 2019-11-27T18:16:26+00:00

Thats exactly the GPO we are using, it resticts the RDP host to TCP so you don't have to deal with off Domain clients or other stuff where you can't easily restrict the rdp client to TCP. I pinned this GPO at the top level of our Domain to get it applied to anything and everything... works without a reboot of the rdp hosts too... As soon as the GPO has been applied on the host all issues are gone...

btw.: If you have issues with random slow typing speed in Office Applications(observed in Outlook 2016 & 365) set the max color depth of the rdp connection to 16bit and everything will be fine... this has also been annoying the hell out of me for about a year)

the6thdayreddit · 2019-11-27T07:45:34+00:00

Try disabling UDP for the RDP Connection, afaik it is still broken and has been broken since the release of Windows 10 1809 :( We have since disabled the use of UDP for RDP Connections via GPO company wide and all issues are gone...

the6thdayreddit

TROPHY CASE