LightBlog

vendredi 30 septembre 2022

If Google wants to be taken seriously, it needs to find ways to assure users it won’t kill new products

Google Stadia is dead, and the funeral is on January 18th, 2023. For now, it’s a walking corpse that users can continue to play on to finish out their games… and then it’ll be gone. Forever. Users will take little solace in the fact that at the very least, they’ll get all of the money they spent on games and hardware refunded to them. If it was the best way for you to unwind in the evening and play some games, that kind of gesture is paltry. What makes it even worse is that ultimately, the fear of Google killing the service is exactly what killed it.

Stadia was proclaimed dead before it was even given a chance

The fear of Google killing Stadia is exactly what killed Stadia

Ever since its inception, naysayers have been trying to make out that Stadia’s days were numbered. After all, Google does have a fairly packed graveyard of messaging applications, a whole social media network that was integrated into YouTube, and several hardware outings such as Google Glass. There’s even a website dedicated to reading about all of the services that Google has laid waste to — aptly dubbed “Killed by Google“. For Stadia, this meant that a lot of people stayed away from it and did not take it seriously, thinking its days were already numbered, which in itself became a self-fulfilling prophecy of doom.

All of this is indicative of a wider problem — Google wants to be taken seriously, but users can’t trust the new products that it launches anymore. If Google plans to launch a new service, people will instantly jump to pessimism. Even in our article covering the launch of Google Stadia, one of the top comments simply states “Can’t wait for this to be sent to the Google Graveyard in a year and a half.” It lasted about twice as long, but the point remains — people just assume new Google services are doomed from the very beginning.

Changing Google’s brand perception on ambitious projects

Google’s biggest issue is that its own brand is now associated with killing services that don’t start on the right foot. If people are afraid to invest in Stadia (for fear of it shutting down), then it’s only going to be a self-fulfilling prophecy. Obviously, people wouldn’t want to invest in a service that everyone sees is doomed to fail. It’s clear that Google needs to find a way past that perception. The problem is: how?

Google Stadia Premiere Edition

One of the best and most consumer-friendly actions that Google has undertaken in this entire debacle is the refunding of all games that users have paid for on the service, even if they’ve played through them. On top of that, all hardware will be refunded too — and that includes the packs which included the likes of a Chromecast. In other words, you still get to keep using some of the stuff, and you basically got it for free.

While I’ll leave it up to the marketing teams to decide how to get this kind of message across, I think a commitment to consumers saying that if it didn’t all work out, they’d get their money back, would have been a good first step. Stadia was seen as a gamble at launch, and I think that users would have been understanding and less fearful if Google did both of the following:

  1. Acknowledged that sometimes business decisions don’t work out.
  2. Committed to refunding users should that business decision not work out.

A common thread of fear I saw interwoven in the discussion of doubt about the now-defunct cloud streaming service specifically pertained to the games that users had paid for. We now have our answer to what those users are getting, but I can’t help but feel that making the commitment early on to that (while acknowledging that some businesses are a risk) wouldn’t have done any less damage than the people who were already expecting canceled projects to be a part of Google’s core. While guaranteeing a refund as an exit strategy isn’t always possible and definitely not the right messaging for any optimistic business, Google needs to be aware of the uniquely negative position that it finds itself in. Showing its hand for an exit strategy may have actually invoked confidence in consumers rather than doubt, as when you’re at rock bottom, reputation-wise, the only way left to go is up.

OnePlus 8 connected to Google Stadia controller Android 11

As for what else the company could have done, I think shutting down SG&E, its first-party games studio, tolled the death knell for many. It was a huge part of the company’s push for cloud streaming, though even at the time Google acknowledged that its white-label service that it offers to companies like Capcom and AT&T for demo purposes was important to its operation. The optics were never good once its own games developer shut down, no matter how many commitments to gamers it made.

Only Google could fail at creating an online gaming service that can play AAA titles and indie favorites during a global pandemic forcing people to use online forms of entertainment, all while a silicon shortage worsened over years and prevented gamers from building high-end computers.

Looking to the future

The more immediate problem for Google is damage control. Projects sometimes don’t work out, and companies all over the world have had to cancel them in order to protect themselves financially. For some reason though, Google has managed to earn its own reputation as one of the worst, and it just keeps getting worse. Microsoft has its own “Killed by Microsoft“, but nobody assumes that Xbox Game Pass Ultimate is currently on a long journey to the morgue.

Galaxy Chromebook 2 with stadia on

Somehow, someway, Google needs to put a stop to the perception that it happily kills services left and right if it ever wants to do anything mildly ambitious. In fact, it doesn’t even have to be ambitious — if Google tries to make another messaging app, it’s going to be dead on arrival. Guaranteed. That’s how terrible the Google brand is for messaging apps, and that reputation will only spread to its other divisions if the company lets it.

Where can Google go from here? It seems the company is damned if it tries anything new and damned to stagnation if it doesn’t even try.

The post If Google wants to be taken seriously, it needs to find ways to assure users it won’t kill new products appeared first on XDA.



from XDA https://ift.tt/db5kj9n
via IFTTT

Windows 11 Update Tracker: Download and Install the latest Windows 11 update

The Windows 11 rollout is going full steam ahead. Microsoft’s next major update for consumers — Windows 11 2022 Update (version 22H2) — is already available via stable channel. However, the OS hasn’t been without issues and the Redmond tech giant is well aware of this fact. The company is periodically rolling out updates for Windows 11 to fix the bugs and introduce new features. This article will serve as the central repository of knowledge base (KB) articles and download links for all updates related to Windows 11.

Table of Contents:

Glossary

Windows updates are compressed in a special archive file format called Microsoft Cabinet (CAB) that supports embedded digital certificates used for maintaining archive integrity. When published via Microsoft Update Catalog, Microsoft often wraps them into the MSU (Microsoft Update) format.

Windows Update MSU CAB

The internal structure of a MSU package

The primary focus of this index is centered around the Cumulative Updates (also known as Monthly Rollups), which include both security and reliability updates that are packaged together. Since they’re cumulative in nature, the latest rollup package has the ability to update the target Windows version to the most recent build, regardless of what the previous build number was.

In some cases, one may need to apply a Servicing Stack Update (SSU) before installing the newest Cumulative Update (CU). The servicing stack is the code that installs other operating system updates, hence Microsoft usually bundles them with CUs before publishing a standalone MSU package. Power users or system admins may still prefer to deal with the CAB variant for ease of deployment. In that case, always install/integrate the SSU before engaging with the CU.

Microsoft also provides CUs for the .NET Framework portion of the Windows OS. Unlike the SSU, they’re distributed separately from the regular CUs.

Windows Feature Experience Pack is yet another type of update that delivers new feature improvements to customers outside of major Windows feature updates.

Then comes the Dynamic Updates (DU) that are meant for the Windows setup engine. They are being automatically downloaded and applied on the fly in order to fix the Windows recovery environment (WinRE), setup binaries, or any files that the Windows setup uses for feature updates. However, we decided not to include them in this index for the sake of avoiding clutters.

To have a clear idea about Windows update terminology, see the article about the types of Windows updates. Keep in mind that an inter-OS (e.g. from Windows 10 to Windows 11) or an inter-build (e.g. from Windows 10 November 2019 Update/Build 18363 to May 2020 Update/Build 19041) update is a way more complex scenario. Microsoft handles such upgrade paths using the Unified Update Platform (UUP), the details of which are not part of this tutorial.


Windows 11 Build index

The following indices are sorted in chronological order. Due to the fact that updates are being pushed from different development pipelines, a higher KB/build number is not always the ideal indicator of the latest build. Please go through the update description before installing.

In some cases, you may find two or more builds are pointing towards the same KB article. This is perfectly normal for bleeding edge releases, as Microsoft is likely to assign the KB number to the latest build that will feature the aggregated fixes.

Build number 22621 (22H2) – Windows 11 2022 Update

Enablement packages

Since the .290 release, Microsoft has decided to split Windows 11 22H2’s Beta channel into two groups. The 22622.x range is meant for bleeding edge users, as these builds will have some bleeding edge features enabled by default. The experimental base has been bumped to 22623.x from the .730 release. The other set of Insiders will stay in build 22621.x, where those new features are turned off.

You can manually switch from 22621.x to 22622.x (or 22623.x) by installing the appropriate enablement package linked below. Note that it requires at least build 22621.285 (for 22622) / 22621.726 (for 22623) to be installed beforehand, but Microsoft never publicly released those versions. Therefore, as long as you have an update with a higher build number installed, you are good to go.

Build KB Download
22621.x to 22623.x KB5018863
22621.x to 22622.x KB5015669

Cumulative update for Windows

Build Changelog and known issues Download
22621.730 and 22623.730 [Tablet-optimized taskbar and more for the Beta channel] KB5017385
22621.525 [Out-of-band September 2022 update] KB5019311
22621.607 [Eighth update for the Release Preview channel] KB5017389
22621.601 and 22622.601 [Multiple fixes for the Beta channel] KB5017384
22621.521 [Seventh update for the Release Preview channel KB5017321
22621.598 and 22622.598 [Multiple fixes for the Beta channel] KB5017390
22621.590 and 22622.590 [Multiple fixes for the Beta channel] KB5017846
22621.586 and 22622.586 [Multiple fixes for the Beta channel] KB5016701
22621.457 [Sixth update for the Release Preview channel] KB5016695
22621.575 and 22622.575 [Multiple fixes for the Beta channel] KB5016694
22621.382 [Fifth update for the Release Preview channel] KB5016632
22621.450 and 22622.450 [Several fixes for the Beta channel] KB5016700

Links for the previous cumulative updates are preserved as well:

Pre-August 2022 Updates

Build Changelog and known issues Download
22621.317 [Fourth update for the Release Preview channel] KB5015885
22621.440 and 22622.440 [New Open with menu and taskbar overflow for the Beta channel] KB5015890
22621.436 and 22622.436 [New sharing features for the Beta channel] KB5015888
22621.232 [Third update for the Release Preview channel] KB5015818
22621.290 and 22622.290 [Second update for the Beta channel] KB5014959
22621.169 [Second update for the Release Preview channel] KB5014958
22621.105 [First update for the Release Preview channel] KB5014688
22621.160 [First update for the Beta channel] KB5014770
22621.4 [Second public cumulative update] KB5015207
22621.3 [First public cumulative update] KB5015207

Cumulative update for .NET Framework 3.5 and 4.8.x

Build Changelog and known issues Download
10.0.9082.6 [Released alongside 22621.521] KB5017026
10.0.9075.8 [Released alongside 22621/22622.575] KB5016591
10.0.9075.6 [Released alongside 22621.382] KB5016717
10.0.9065.6 [Released alongside 22621/22622.440] KB5015734
10.0.4460.20 [Released alongside 22621.1] KB5007297

Build number 22000 (21H2) – Windows 11 (original release)

Cumulative update for Windows

Build Changelog and known issues Download
22000.1042 [Optional September 2022 update] KB5017383
22000.1041 [Multiple fixes for the Release Preview channel] KB5017383
22000.978 [September 2022 update] KB5017328
22000.918 [Optional August 2022 update] KB5016691
22000.917 [Remote admin-assisted language installation facility for the Release Preview channel] KB5016691
22000.856 [August 2022 update] KB5016629

Links for the previous cumulative updates are preserved as well:

Pre-August 2022 Updates

Build Changelog and known issues Download
22000.832 [Optional July 2022 update] KB5015882
22000.829 [OOBE update facility for the Release Preview channel] KB5015882
22000.795 [July 2022 update] KB5015814
22000.778 [Optional June 2022 update] KB5014668
22000.740 [Out-of-band – Fix for Azure Active Directory (AAD) signing issue on ARM-based devices] KB5016138
22000.776 [Search highlights for the Release Preview channel] KB5014668
22000.739 [June 2022 update] KB5014697
22000.708 [Optional May 2022 update] KB5014019
22000.706 [Windows spotlight for desktop and more for the Release Preview channel] KB5014019
22000.675 [May 2022 update] KB5013943
22000.652 [Optional April 2022 update] KB5012643
22000.651 [Secure Boot component servicing improvements and more for the Release Preview channel] KB5012643
22000.613 [April 2022 update] KB5012592
22000.593 [Optional March 2022 update] KB5011563
22000.588 [Notification improvements and more for Beta and Release Preview channels] KB5011563
22000.556 [March 2022 update] KB5011493
22000.527 [Optional February 2022 update] KB5010414
22000.526 [Weather content on the taskbar for Beta and Release Preview channels] KB5010414
22000.493 [February 2022 update] KB5010386
22000.469 [Multiple fixes / Optional January 2022 update] KB5008353
22000.467 [Out-of-band – Fix for Windows Retail Demo Mode] KB5010690
22000.438 [Out-of-band – Fix for VPN issues] KB5010795
22000.466 [Multiple fixes for Beta and Release Preview channels] KB5008353
22000.434 [January 2022 update] KB5009566
22000.376 [December 2021 update] KB5008215
22000.348 [Fix for issues related to the Microsoft Installer / Optional November 2021 update] KB5007262
22000.346 [Fluent emoji for Beta and Release Preview channels] KB5007262
22000.318 [November 2021 update] KB5007215
22000.318 (Feature Experience Pack only, major build number is still 22000.282) [Fix for expiring app certificates] KB5008295
22000.282 [Fix for AMD issues] KB5006746
22000.258 [October 2021 update] KB5006674
22000.194 [Integrated with Insider Preview 11 and the General Availability build] KB5005635
22000.184 [Integrated with Insider Preview 10] KB5005642
22000.176 [Integrated with Insider Preview 9] KB5006050
22000.168 [Integrated with Insider Preview 8] KB5005191
22000.160 [Integrated with Insider Preview 7] KB5005189
22000.132 [Integrated with Insider Preview 6] KB5005190
22000.120 [Integrated with Insider Preview 5] KB5005188
22000.100 [Integrated with Insider Preview 4] KB5004300
22000.71 [Integrated with Insider Preview 3] KB5004252
22000.65 [Integrated with Insider Preview 2] KB5004745
22000.51 [Integrated with Insider Preview 1] KB5004564

Cumulative update for .NET Framework 3.5 and 4.8

Build Changelog and known issues Download
10.0.4566.2 [Released alongside 22000.1042] KB5017264
10.0.4556.3 [Released alongside 22000.978] KB5017024
10.0.4550.1 [Released alongside 22000.918] KB5016594

Links for the previous .NET Framework 3.5 and 4.8 cumulative updates are preserved as well:

Pre-August 2022 Updates

Build Changelog and known issues Download
10.0.4536.3 [Released alongside 22000.832] KB5015732
10.0.4515.1 [Released alongside 22000.708] KB5013889
10.0.4510.2 [Released alongside 22000.675] KB5013628
10.0.4501.1 [Released alongside 22000.652] KB5012159
10.0.4494.3 [Released alongside 22000.613] KB5012121
10.0.4488.1 [Released alongside 22000.527] KB5010474
10.0.4470.1 [Released alongside 22000.469] KB5009469
10.0.4465.6 [Released alongside 22000.434] KB5008880
10.0.4455.1 [Released alongside 22000.348] KB5007292
10.0.4435.1 [Released alongside 22000.282] KB5006363
10.0.4420.2 [Released alongside 22000.258] KB5005537
10.0.4400.3 [Released alongside 22000.100] KB5004342
10.0.4395.3 [Released alongside 22000.51] KB5004034

(Optional) .NET Framework 4.8.1

Since August 2022, a standalone .NET Framework 4.8.1 update is available for Windows 11 as well as Windows 10. Since Microsoft offers cumulative updates for .NET Framework 4.8.1 independently from the 4.8 branch, we list them in a separate index below. The base CAB packages and the offline installer are build-agnostic, hence you can install them on both Windows 11 and Windows 10.

Build Changelog and known issues Download
4.8.9037.0 [August 2022] KB5011048

(Optional) Cumulative update for .NET Framework 3.5 and 4.8.1

Build Changelog and known issues Download
10.0.9093.1 [Released alongside 22000.1042] KB5017267
10.0.9082.7 [Released alongside 22000.978] KB5017029

How to install the Windows 11 cumulative updates

CAB packages

To install a CAB update package, you need to use a built-in system utility called Deployment Image Servicing and Management (DISM). The command-line syntax should be as follows:

dism /online /add-package /packagepath:<path_to_cabfile>

Windows 11 DISM CAB Install

CAB and PSF packages

Since Windows 10 Insider Preview Build 21382, Microsoft has made a significant change in the Latest Cumulative Update (LCU) format. As a result, the end user can’t use the CAB file directly. To perform the installation using the built-in update module, the corresponding Patch Storage Files (PSF) package must be present. This is the exact reason one can find PSF files corresponding to each LCU in the Windows 11 UUP Dump. In case of an online installation, Windows Update only downloads and generates missing PSFX (PSF Express) payloads, while the CAB package only contain the manifests.

However, DISM alone can’t handle the PSF packages, which means we need to somehow combine the PSF and CAB files manually before trying to install them offline. Fortunately, there exists an open source tool named PSFX Repack for this job.

  • Extract the archive of the PSFX Repack tool to a folder with a short path (like “D:\PSFX_Repack\”).
  • Download both CAB and PSF files corresponding to the SSU and LCU and move them to the aforementioned folder. Kindly refer to the above index to note down appropriate the KB number before downloading.
    • You can remove the hash (if present) from the file names so that the file set looks like Windows10.0-KBxxxxxxx-x64.cab and Windows10.0-KBxxxxxxx-x64.psf. This step is optional, as the latest version of the PSFX Repack tool can handle the new naming scheme out of the box.
  • Run psfx2cab_CLI.cmd to generate the combined CAB file.

Windows LCU PSFX Repack

  • Use DISM to install the latest SSU CAB first, then the resultant LCU CAB file.

LCU PSFX Repack install DISM

MSU packages

The MSU variant, on the other hand, is somewhat standalone in nature due to the fact that one can simply double-click on it to install the package. Note that DISM can also install MSU files.

MSU Install 1 MSU Install 2 MSU Install 3

After the installation finishes, you will be prompted to restart the PC for the changes to take effect.


Verification

The Settings app in Windows 11 has an option to view the list of updates installed on your PC. Here’s how to access it.

  • Open Settings and click Windows Update.
  • Click/tap on Update history.

Windows 11 Settings Update history page

The good old Programs and Features applet in the classic Control Panel can also show you the list of installed updates.

  • Right-click Start, click Run.
  • Type appwiz.cpl and click OK. This opens the Programs and Features in the classic Control Panel.
  • Click the View installed updates link on the left side. This shows you the list of updates along with the installation date column.

Windows 11 Control Panel Installed Updates

If the command-line is your thing, then you can opt for DISM or Windows Management Instrumentation (WMIC) as well. You need to execute the command from an elevated instance of Windows Terminal.

  • Using DISM:
dism /online /get-packages /format:table | findstr "Package_for"

Windows 11 DISM installed updates

  • Using WMIC:
wmic qfe

Windows 11 WMIC installed updates


We hope this article not only serves as a common update index for Windows 11 but also provides general installation instructions that can be useful for other Windows builds as well. We’ll be updating this guide with links to newer Windows builds, so check back again in the future!

The post Windows 11 Update Tracker: Download and Install the latest Windows 11 update appeared first on XDA.



from XDA https://ift.tt/LNcAYfk
via IFTTT

Here are the best Samsung Galaxy S22 screen protectors to buy in 2022

At its first Galaxy Unpacked event of 2022, Samsung lifted the covers off its latest flagship smartphone lineup. The Galaxy S22 series includes three devices — the regular Galaxy S22, the Galaxy S22 Plus, and the Galaxy S22 Ultra. Being the cheapest one of the lot, the vanilla Galaxy S22 attracted a ton of buyers, even though it only offers minor improvements compared to the Galaxy S21 from last year.

If you’re one of the many people who bought the device or are waiting for a great deal on the Galaxy S22 to pick it up at a discount, we recommend you get a screen protector to keep it safe from scratches and cracks. In this post, we’ve curated a list of the best Galaxy S22 screen protectors that you should get if you want to keep your new phone’s display looking good in the months to come.

Best Galaxy S22 Screen Protectors

    Spigen NeoFlex

    Premium TPU screen protector

    The Spigen NeoFlex is a premium TPU screen protector that offers a crystal clear finish and comes with an easy, bubble-free installation solution.
    Spigen Tempered Glass

    Smooth to the touch

    Unlike the NeoFlex screen protector, Spigen's Tempered Glass screen guard for the Galaxy S22 offers a smooth feel, thanks to its glass surface. It also comes with an auto-alignment installation kit.
    Milomdoi Tempered Glass

    Affordable overall protection

    The Milomdoi tempered glass screen protector is an affordable option that comes with three tempered glass screen protector and two camera lens protectors.
    Supershieldz Tempered Glass

    Another affordable pick

    The Supershielz tempered glass screen protector for the Galaxy S22 is another affordable option that includes three temepered glass screen protectors for under $10.
    Magglass Screen Protector

    Premium screen and camera glass protector

    The Magglass tempered glass screen protector for the Galaxy S22 includes a glass screen protector, a camera guard, and an easy application tool.
    ArmorSuit MilitaryShield

    Self-repair

    If you're not a fan of tempered glass screen protectors, you can get the ArmorSuit MilitaryShield screen protector instead. It's a clear film screen protector that features self-healing properties.

That rounds up our list of the best Galaxy S22 screen protectors on the market. If you don’t like any of the options mentioned above and just want to get a cheap film-type protector that you can change often, get the Supershieldz PET screen protector for the Galaxy S22. A six-pack of the Supershieldz PET screen protector costs just seven bucks, and it’s a great alternative for those who get scratches on the display quite frequently. Since I’m not a fan of applying screen protectors, I’d personally go with the Spigen Tempered Glass Screen protector. That’s because it comes with a handy tool that makes the process a whole lot easier.

Which one of these options will you pick and why? Make sure to let us know in the comments section below. Also, check out our roundup of the best Galaxy S22 cases, if you want to add an additional layer of protection to your brand new device. We have quite a few options, ranging from rugged cases that provide maximum protection to clear cases that highlight the colors of your Galaxy S22.

    Samsung Galaxy S22
    Although the new Galaxy S22 features a 6.1-inch FHD+ AMOLED display with Corning's Gorilla Glass Victus+, you should still invest in a screen protector for peace of mind.

The post Here are the best Samsung Galaxy S22 screen protectors to buy in 2022 appeared first on XDA.



from XDA https://ift.tt/vcZnF1f
via IFTTT