On 2025-01-13 07:40, RonB wrote:
> On 2025-01-12, CrudeSausage <crude@sausa.ge> wrote:
>> On 2025-01-12 03:38, RonB wrote:
>>> On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote:
>>>> On 2025-01-11 04:27, RonB wrote:
>>>>> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote:
>>>>>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/>
>>>>>>
>>>>>> Microsoft will force install the new Outlook email client on Windows 10
>>>>>> systems starting with next month's security update.
>>>>>>
>>>>>> The announcement was made in a new message added to the company's
>>>>>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft
>>>>>> 365 apps users.
>>>>>>
>>>>>> As Redmond explains, the new Outlook app will be installed on Windows 10
>>>>>> devices for users who deploy the optional January 28 update and force
>>>>>> installed for all who install the February 11 security update.
>>>>>>
>>>>>> The new Outlook client will run alongside the classic Outlook app and
>>>>>> will not modify configurations or user defaults. Microsoft added that
>>>>>> there's no way to block it from being installed on Windows 10 devices;
>>>>>> however, those who don't want it can remove it afterward.
>>>>>>
>>>>>> "New Outlook exists as an installed app on the device. For instance, it
>>>>>> can be found in the Apps section of the Start Menu. It does not replace
>>>>>> existing (classic) Outlook or change any configurations / user defaults.
>>>>>> Both (classic) Outlook and New Outlook for Windows can run side by
>>>>>> side," Microsoft says.
>>>>>>
>>>>>> "Currently, there isn't a way to block the new Outlook from being
>>>>>> installed - if you prefer not to have new Outlook show up on your
>>>>>> organization's devices, you can remove it after it's installed as part
>>>>>> of the update," the company added in a support document updated on Thursday.
>>>>>>
>>>>>> New Outlook user interface
>>>>>> New Outlook user interface (Microsoft)
>>>>>> To remove the new Outlook app package after it's force installed on your
>>>>>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet
>>>>>> with the PackageName parameter value Microsoft.OutlookForWindows.
>>>>>>
>>>>>> This can be done by running the following command from a Windows
>>>>>> PowerShell prompt and adding a new reg value:
>>>>>>
>>>>>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName
>>>>>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName
>>>>>>
>>>>>> REG VALUE:
>>>>>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate
>>>>>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a
>>>>>> value of ["MS_Outlook"]. After removing the Outlook package, Windows
>>>>>> Updates will not reinstall the new Outlook client.
>>>>>>
>>>>>> The first preview version of the new Outlook for Windows was introduced
>>>>>> in May 2022. The app was generally available for personal accounts in
>>>>>> September 2023 (via the September 26 Windows fall update and the
>>>>>> Microsoft Store on Windows 11) and for commercial customers in August 2024.
>>>>>
>>>>> Even if I used Windows I wouldn't use Outlook.
>>>>
>>>> If you use a Microsoft account, the new Outlook is light enough to be
>>>> fun to use. It's a lot less clunky than the older Outlook application
>>>> albeit not as functional. Still, I would rather these people actually
>>>> give me a choice as to whether I have the program on my computer or not.
>>>> I quite like how I can remove anything and everything from a Linux
>>>> installation.
>>>
>>> Light or not light, I have zero interest in Outlook. I never even used it
>>> when I used Windows.
>>>
>>> Speaking of Windows... my son's Windows 10 computer was hosed (probably
>>> because he wouldn't let it update). So we got him an SSD where I was
>>> planning on doing a new install. I thought I was using a Windows 10 USB for
>>> the install, but apparently it was Windows 11 from 2022. At any rate it
>>> installed and updated, but threw an error (can't update).
>>>
>>> TPC 2.0 wasn't turned on in the BIOS, which was required to get it past a
>>> certain point. So I turned that on, still wouldn't update. So I finally
>>> found out I had to use one of the options on Microsoft's download page to
>>> update it. It got to about 76% (or so) and the update stopped because the
>>> NVMe's firmware wasn't updated(?). Really? The damned firmware not being
>>> updated on the (obviously) working SSD and Windows 11 wouldn't update? Is
>>> this the kind of crap everyone is going to run into when trying to update to
>>> Windows 11 from Windows 10?
>>
>> If the firmware were a problem, the computer should not have even
>> allowed the SSD to be detected. Either way, you can use a Linux live
>> environment to either use fwupd or the GUI alternative and update the
>> firmware before trying again. I notice fwupd is much better than
>> Microsoft or ASUS's own tools when it comes to updating secure boot.
>
> I totally agree. And why doesn't Windows check all the requirements BEFORE it
> spends an hour or an hour and a half "installing." How stupid are these
> people? I had no idea TPM was shut in the BIOS. I forgot to mention that,
> since we couldn't fix the issues with Windows 10 on the hard drive, I had to
> buy another license for Windows 11, so now the the same computer has two
> licenses. I just found out that a different son has been using an
> "unactivated" Windows install since he replaced his motherboard. Fortunately
> you can pick up these license keys on eBay for about $5 to $10 (and I don't
> feel bad at all about it). I think it's stupid to have to re-license a
> computer that's already licensed.
>
> Just more reasons to hate hobbyware Windows.

I actually lose the Windows 10 license that was attached to this
computer when they replaced the motherboard, but I don't really care. I
have a 10 Pro license I can use whenever I want if I really insist on
having Windows on the machine. However, I like Fedora, a lot. Everything
but the fingerprint reader works as it should and I can even play my
games (I'm not even using compatibility at this point, I'm focusing on
the ones which have a native Linux edition). I don't have access to a
lot of my movies anymore, but that's fine: I have them on the Xbox
Series S and they're still attached to my account anyway. If Microsoft
one day wakes up and smells the coffee and starts offering them on the
web like everyone else, I'll have access to them on Linux too. It is
just refreshing after three years to know that I _can_ escape the
dreaded stuttering I was having in Windows. Nobody knew what it was and
nobody would admit to it happening, until someone pin-pointed the
problem and forced AMD to admit to it. Meanwhile, it still isn't fixed
on laptops and you are forced to use the machine knowing that
occasionally, the sound, mouse cursor and video will chop for 2-3
seconds at a time. The mere fact that they won't fix a _known_ problem
is evidence that they don't deserve the support.

>>> Anyhow I downloaded and installed the firmware for the WD Blue SSD (when did
>>> San-disk buy Western Digital?) and hit the "Refresh" button on the install
>>> page. Hit it again... and again... and again... Zero response. So I had to
>>> start the install again. Of course it stopped — again — with the SSD
>>> firmware issue. I realized ah, crap, I'll have to restart the computer.
>>> (Crappy Windows) before it will see the firmware update. It took forever
>>> again, but the update finished with only one more restart... and about
>>> another fifteen minutes of waiting. But, *finally* the update was
>>> complete... wait a minute, Windows immediately started downloading the next
>>> update... so I guess the loop goes on and on.
>>>
>>> Windows 11 updates may be better than than Windows 10 ones, but it's still
>>> total crap compared to Linux.
>>
>> Well, possibly. However, whenever I update this Fedora installation, it
>> refuses to restart, I have to force it to shut down and then have to
>> rebuild the NVIDIA driver. It's annoying, but I can live with what is
>> essentially a daily frustration.
>
> I haven't had these kinds of problems with Fedora (or Linux Mint) but I have
> simple machines — as mentioned many times. If Fedora gives you that trouble
> every time you update it, I would only update it every other week or so.
> Maybe every third week.

I think the problem was caused by my switching over to S3 suspend, at
some point. Linux can manage through it, but I believe that the settings
ended up being screwed up, even after I reverted back to S0. I took the
opportunity to try OpenMandriva yesterday (it's fine), before
reinstalling Fedora. It seems to be working right now.

--
CrudeSausage
Gab: @CrudeSausage
Unapologetic paleoconservative