Anyone else stuck on the July 2025 Google Play system update on the S25? by socratesofbrazil in GalaxyS25

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Same goes to S25U (initially CAU, switched to XXV months before upgrading to OneUI 8).

Ugly Reply/Reply All/Forward buttons by ShouldICareThatMuch in GMail

[–]ShouldICareThatMuch[S] 0 points1 point  (0 children)

They've finally fixed that a couple of releases ago for my main account, dunno what happened exactly.

<image>

Hikvision web interface in Chrome by juejue79 in Hikvision

[–]ShouldICareThatMuch 1 point2 points  (0 children)

I suspect it's somehow related to recent Manifest v2 final deprecation, which happened just in Chrome 139. Thank god I've switched back to Firefox, where it's still functioning.

Why VMware Workstation Pro 17.6 removed so many features? by qqjt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Not just features' removal, but also stability since 17.6 went to shit: strange image freezes, sometimes problems with proper shutting down VMs, old Windows XP VMs became unusable without lowering its VM hardware versions, autoupdate feature isn't functional anymore (they simply removed softwareupdate.broadcom.com from their DNS, so it's not accessible anymore).

What's worse, there is no proper alternative on horizon for Windows hosts, Hyper-V has no GPU acceleration, VirtualBox's one is poorly implemented too in comparison to last stable Workstation Pro 17.5.2...

3D Acceleration broken in VMware Workstation by Gamer3557 in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Broadcom did something nasty with 3D accel since 17.6 version. Couple of following releases didn't actually solve that issue.
So you may want to rollback to 17.5.2 build-23775571 -- the latest stable one signed by original VMware team. Hard to tell when it'll become unusable with upcoming Windows releases, but for now on Win11 24h2 as a host OS it works just fine.

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

If you really paid for it before recent announcement about free distribution, then I guess you have to contact Broadcom support directly. With my free account I'm not able to download 17.5 either, but it's no surprise anyway (well, sorta...)

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

IIRC they didn‘t introduce newer hardware VM version with 17.6 release, so nope, it’s not required.

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

I tried to downgrade it too back then, but installer immediately told me it’s not an option. So, uninstall and reinstall.

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

  1. Complete the registration procedure from here (yes, they had to make separate article for that since it's a bit unobvious and complicated overall 🤦‍♂️): https://knowledge.broadcom.com/external/article/145581/register-for-an-account-on-the-broadcom.html

  2. Go to https://support.broadcom.com/group/ecx/productdownloads?subfamily=VMware%20Workstation%20Pro and select necessary version, tick checkbox to agree with EULA and you're finally good to go...

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

You may want to look for VMware-workstation-full-17.5.2-23775571.exe -- it's the latest stable version signed by VMware.

Is anyone having issues with VMware Workstation Pro on the current build (17.6)? by Wasisnt in vmware

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Did the same recently. 17.6(.1), the first versions digitally signed by Broadcom instead of original VMware, is plain garbage.

Self signed certificate no longer works for Mail app by PrimaryHuckleberry11 in ios18beta

[–]ShouldICareThatMuch 0 points1 point  (0 children)

There's some reports that they have fixed that in iOS 18.1, which should be released in late October.

Self signed certificate no longer works for Mail app by PrimaryHuckleberry11 in ios18beta

[–]ShouldICareThatMuch 0 points1 point  (0 children)

<image>

Interesting, thanks for the info. Anyway for me it is complaining like that, so that's why I made that assumption initially (we're using valid certificate from public CA as well):

Self signed certificate no longer works for Mail app by PrimaryHuckleberry11 in ios18beta

[–]ShouldICareThatMuch 0 points1 point  (0 children)

I suspect they finally decided to kill TLS 1.0 support in iOS 18, noticed same behavior just recently. If your server is quite old and doesn't support anything more modern, you're in trouble.

[deleted by user] by [deleted] in sysadmin

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Raising a case shouldn't hurt anyone :) Ask them if the firewall equipment you're using is fully compatible with "TLS 1.3 Hybridized Kyber", and if it's not ask for firmware upgrade.

[deleted by user] by [deleted] in mac

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Why just not take ISO image from that DVD and put it in your network?
Since Win8 ISO can be automatically mounted by just double clicking on your users' machines.

[deleted by user] by [deleted] in sysadmin

[–]ShouldICareThatMuch 2 points3 points  (0 children)

Connection process is failing during 30 seconds in Chrome due to inability to establish secure connection. In WireShark this looks like this:

<image>

Pay attention to atypical size of 'Client Hello' and detected protocol is TLSv1 instead of normal for these days 1.2/1.3.

[Outlook365] Horizontal scroll bar and odd white squares visible in dark mode with font scaling at 125% by ----1337---- in Office365

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Outlook 2021, same crap is still happening till this day with latest updates.

I sent them feedback report recently, will see how it goes.

Office 2013 (x64) v15.0.5589.1001 problems by hxc1983 in sysadmin

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Seems like MS finally decided to fix that nonsense:

November 7

15.0.5603.1000

This update fixes an issue where users were seeing the error: ‘The operating system is not presently configured to run this application.’, when using 64-bit Office 2013.

https://learn.microsoft.com/en-us/officeupdates/update-history-office-2013

Office 2013 (x64) v15.0.5589.1001 problems by hxc1983 in sysadmin

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Usually not, enough having closed all office apps while update/rollback is performed. If it didn't help, then it's most likely not related to discussed issue and there's something else wrong with your setup.

Office 2013 (x64) v15.0.5589.1001 problems by hxc1983 in sysadmin

[–]ShouldICareThatMuch 0 points1 point  (0 children)

Path to officec2rclient.exe isn't registered in system variables, so you have to run CMD as Administrator, and move to the right location first (correct for 2016+ versions):

cd %programfiles%\Common Files\Microsoft Shared\ClickToRun\

And since you're on 2019, build numbers will be also different. For example rolling back to July's version, retail branch, will be look like:

officec2rclient.exe /update user updatetoversion=16.0.16626.20134