It’s been more than two years since the release of Windows 11, but a huge chunk of users are still using Windows 10. Microsoft announced that Windows 10 will reach the end of support (EOS) on October 14, 2025, and slowly started urging users to shift to the latest version, i.e., Windows 11.

Despite offering a free upgrade, users prefer to stick to Windows 10, at least until the dreaded EOS date arrives. You can upgrade to Windows 11 or stick to Windows 10 by clicking the “Keep Windows 10” option.

1 of 4

As you can see in the above screenshots, Microsoft is pushing Windows 11 through a four-page long pop-up:

• First screen: Microsoft is telling you that your computer can switch to Windows 11 for free. You can still use your computer while it sets up the new system in the background, and it won’t take up much space.
• Second screen: Microsoft recommends switching to Windows 11 because it’s a smooth change. Your stuff will move with you, and the design is easy to get used to.
• Third screen: This message introduces Windows 11 as a fun upgrade with a new look, better security, and speed. It’s designed to be easy to use and helps you work and play better. They also note that some things from Windows 10 might not be in Windows 11.
• Fourth screen: Finally, Microsoft is telling you that you can stay with Windows 10 if you want, but they remind you that you can upgrade to Windows 11 for free.

But why aren’t users shifting to Windows 11, which promised to offer a lot (better UI, improved system apps, and full-blown AI assistant integration)?

For some, it is the lack of stability; for others, it is the lack of support for older hardware. Windows 11’s stern requirement of a TPM 2.0 chip obstructs the installation for many users.

Even if the PC has impressive specs, older or missing TPM chips deter them from using Windows 11.

There is a way around TPM and Secure Boot, but that beats the point of switching to the new operating system and not having the most-talked-about security features.

Windows 10 commands a ginormous user base

You might think that most users must have hopped to Microsoft’s latest and greatest OS offering after seeing the ads, but sadly, that isn’t the case. StatCounter reports that Windows 10 still has a 66.43 percent market share in contrast to Windows 11’s 27.82 percent market share.

However, Windows 11’s market share displayed a small increase from 26.63 to 27.82 percent after the September 2023 update, which integrated Copilot. Windows 10 showcased a steep downfall from 71.6 percent to 66.43 percent during that time, even after Microsoft released Copilot for it.

This small increase indicates that users are upgrading to Windows 11 (either by updating their PCs or allured by the feature add-ons).

However, 66.43 percent of users are still on Windows 10, so Microsoft might consider extending the EOS date. Otherwise, more than 60 percent of Windows users will receive no updates, which will cause a rise in security incidents.

We are still determining whether Microsoft will slow down the pop-ups or adopt a more coercive upgrade strategy. However, the ad menace aggravates many users who might even consider moving to alternatives like Linux when the time arrives.

The post Microsoft again reminds Windows 10 users it’s time to get Windows 11 with renewed pop-ups appeared first on Windows Latest

So what went wrong? According to reports on Feedback Hub and Microsoft’s forums, Microsoft auto-updated its inbox apps via its Store on January 23. While the updates were supposed to be regular maintenance releases, they broke the inbox apps like Microsoft Photos, Calculator, Mail and Calendar, Feedback Hub, and more.

Based on the reports we’ve received from users, these apps immediately crash upon launching with an error message “File system error (-2147219196)”. This bug seems to affect older hardware only, such as AMD Athlon, Intel Quad, and Core 2 Duo processors, which were in the market in the early 2000s.

“Once you have an update, you can’t go back. Microsoft does this, and on top of that, without warning is a dirty move,” one frustrated user noted in a Feedback Hub post.

Another user explained the problem: I am experiencing the same issue. Microsoft Photos worked yesterday, but it is giving the same “File System Error (-2147219196)” on Windows 10 Pro on 1 PC, but it is still working on another.

Why Windows 10 apps are crashing with File System Error (-2147219196)?

The root cause of the issue lies within a critical package, “vclibs framework”, used by several inbox apps. This package contains libraries that help Microsoft Inbox apps like Photos and Calculator run correctly.

Recently, a change in the vclibs framework inadvertently made these apps require SSE4.2 instructions.

As Wikipedia notes, SSE has been around for decades, but version SSE4.2 shipped much later in 2011 and is not supported by older processors. SSE4.2 helps a computer’s processor handle data more efficiently, leading to better performance when opening apps.

Microsoft accidentally made SSE4.2 a mandatory requirement for vclibs framework. As a result, Windows 10 PCs with older processors, which lack SSE4.2 support, are unable  to launch the following apps:

• Photos
• Calculator
• Mail & Calendar
• Film & TV (aka Movies & TV).
• Feedback Hub.
• Paint 3D.
• 3D Viewer.
• Game Bar

That’s because older processors cannot handle or execute the SSE4.2 instructions for the apps, which are now “accidentally” required by the vclibs framework.

In a statement, a Microsoft support staff confirmed it’s aware of the issue, and new app packages containing the fix will begin rolling out via the Windows Store in the coming hours.

It’s worth noting that these processors are officially unsupported, but some people still run Windows 10 on them.

Unlike other tech companies, Microsoft has a good track record of maintaining backward compatibility. Windows 10 remains supported until October 2025, and this error appears to be a genuine mistake by the Visual Studio team.

The post Microsoft confirms Windows 10 File system error (2147219196) crashing apps appeared first on Windows Latest

According to our tests, apps like Google Chrome open with a blank or white screen, and relaunching the browser or restarting the system does not resolve the problem. Many of our readers confirmed that uninstalling the Windows 10 Server 2022 KB5034129 update allows them to access the affected apps again.

KB5034129 is a mandatory security update for administrators as it fixes critical security issues, which is why many installed the patch when it was released. However, after installing the update, some admins tell us they can not use Google Chrome, Edge, or Firefox. We’ve also seen reports of the bug affecting Adobe software.

The issue has also been reported on Feedback Hub and Mozilla’s Bugzilla forum.

The good news is Microsoft is looking into the reports, and the company tells me it will share more details soon.

At the time of writing, the tech giant hadn’t acknowledged the report in its support document, but users continued to run into the issue.

My tests suggest the issue is related to a GPU load failure. When graphics do not load, you will see a blank screen when accessing apps like Google Chrome or Edge.

We don’t believe the issue is limited to browsers, but you’re more likely to run into a white screen bug when opening Chrome or Edge. Sometimes, the problem is also experienced when accessing Windows Search, Adobe apps, or the Snipping Tool.

How to fix Chrome or Edge white screen issue in Windows Server 2022 update

Some people have uninstalled KB5034129 to restore Chrome or Edge on Windows Server, but if you do not want to revert the critical security fixes, you can make one change to Windows Registry to fix the mess.

For example, if Chrome is crashing with a white screen, you can remove the registry key “chrome.exe” located inside the following directory:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options

We’ve also created a PowerShell script that automates the process:

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\chrome.exe" /f

In the above script, you can replace Chrome.exe with MSEdge.exe if you cannot launch Edge.

Or, if you do not want to delete a registry key, try renaming msedge.exe to something like edge_test.exe, and Edge will launch again.

The January 2024 update has a nasty surprise for everyone, including those on Windows 10 and Windows 11.

The post Microsoft is investigating Windows Update breaking apps on Windows Server 2022 appeared first on Windows Latest

KB5034129 for Windows Server 2022 is a mandatory Patch Tuesday 2024 update that breaks Microsoft Edge, Chrome and Firefox. Enterprises and individuals report that their browsers and apps like Adobe now open with a blank window. This has been confirmed by Windows Latest in our tests.

Microsoft released the KB5034129 update for Windows 10-based Windows Server 2022 on January 9 with several improvements. This includes fixes for issues that affect InTune or hybrid joined devices. It also fixed a bug where Microsoft Excel stops responding when you try to share an Excel sheet as a PDF in Outlook.

KB5034129 is a mandatory update, and most of the companies have rushed to install it as it fixes the Wi-Fi adapter issues. However, many people told us the Windows Server 2022 update causes browsers like Microsoft Edge, Google Chrome, and Mozilla’s Firefox to open with a blank white page.

In one example, a user explained that Edge consumed about 50% of CPU usage with 12 Edge processes and 8-10 Windows error reporting processes running. This issue also led to disk space filling up, but it only affected some of their terminal servers.

Following the update, Chrome would open to a blank screen, and logging indicated a GPU load failure. Attempts to fix the issue, including updating VMWare Tools, trying the latest Chrome Beta, and reinstalling Chrome, were unsuccessful. The only solution was to remove the problematic update.

According to a bug post on Mozilla forums, this bug also affects Firefox.

In our tests, we discovered that removing the registry key “chrome.exe” found at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options resolves the issue.

Or you can open PowerShell and run the following command to delete the .exe:

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\chrome.exe" /f

You can also rename chrome.exe to something like chrome_test.exe, and Chrome will start working again.

These steps do not require a reboot and work in most cases.

Other problems with KB5034129

Additionally, some of our readers are encountering installation issues with KB5034439 and KB5034129

They reported error code 0x80070643 and problems when installing the security patch, even on newly built Server 2022 VMs from the official ISO. These VMs have a standard 200GB virtual HDD with a 573MB recovery partition, indicating that the issue is not related to imaging or a flawed base image.

In our tests, we noticed that the issue is experienced when the system detects a recovery partition with low storage. You can fix it by increasing the partition size, or you can use the PowerShell script uploaded to our Discord server’s Windows 10 channel.

Before running the script, you must download and install the Safe OS Dynamic Update from the Microsoft Update Catalog. Once done, run the PowerShell script, which applies the Safe OS update, and patches the installation errors by reconfiguring BitLocker.

The post Windows Server 2022 KB5034129 crashes Edge, Chrome and Firefox with white screen appeared first on Windows Latest

On January 9, Microsoft published a cumulative update KB5034441 to fix security issues in the Windows Recovery Environment (WinRE), which powers your recovery partition. This mandatory security update patched a critical issue that could allow attackers to bypass BitLocker encryption and access your sensitive files by exploiting WinRE.

Unfortunately, many people told us they could not install Windows 10 KB5034441 due to the 0x80070643 error. In Feedback Hub and our comments section, many users complained the update is constantly failing. One person said they tried many things, like reinstalling Windows, but nothing worked.

Additionally, another user detailed their unsuccessful experience with the January 2024 security update for Windows 10, version 22H2, on x64-based systems. Despite using the Windows Update troubleshooter to fix corruption, the update still failed to install, posing a significant inconvenience.

In our tests, we observed that the update fails to install when it detects the recovery partition drive does not have sufficient free space. As per updated documents, Windows recovery partitions must have at least 250 MB of free space.

Why is the Windows 10 KB5034441 update failing with the 0x80070643 error

We reached out to Microsoft, and the company confirmed it’s aware of the reports that some people cannot install KB5034441 due to error 0x80070643.

The tech giant has said that the issue might be because there’s not enough space in a part of Windows called the Windows Recovery Environment (WinRE). This partition now needs at least 250 megabytes of free space.

If you run into error 0x80070643 when installing the latest update, you may need to increase the size of the WinRE partition and check for updates again. Additionally, Microsoft clarified that new WinRE updates now require 250MB of free space in the recovery partition.

How to fix the 0x80070643 ERROR_INSTALL_FAILURE issue

To fix the 0x80070643 error, you can make the partition bigger, and we have a simple guide to do that:

1. Open Command Prompt (cmd) as an administrator.
2. Check if WinRE is installed by running reagentc /info. If it’s there, you’ll see a “Windows RE location” with a path.
3. Turn off WinRE by running reagentc /disable.
4. Get ready to make a new recovery partition by shrinking the OS partition.
5. Use diskpart by running diskpart in Command Prompt.
6. List the disks and select the one with OS by running the command sel disk<OS disk index>.
7. Find and select the OS partition by running the command sel part<OS partition index>.
8. After selecting the partition, run the command: shrink desired=250 minimum=250.
9. Select and delete the old WinRE by running the command: sel part<WinRE partition index>, and then run the command delete partition override.

Finally, you can create a new recovery partition. In this step, check if your disk is GPT (GUID Partition Table) or MBR (Master Boot Record) by running the list disk. When you run the list disk command, you’ll see a new list of drives. A drive is “Gpt” if you see an asterisk (*) in the “Gpt” column.

If you do not see the asterisk mark, the drive is MBR.

For GPT, use the following commands:

 create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

After running the above command, run gpt attributes =0x8000000000000001.

For MBR, run create partition primary id=27 and follow these steps:

• Format the new partition: format quick fs=ntfs label=”Windows RE tools”.
• Check the new partition with list vol and exit diskpart with exit.
• Turn WinRE back on with reagentc /enable.
• Confirm WinRE installation with reagentc /info.

In some cases, you might face an error “Windows RE image was not found” during the reagentc /enable process. Thankfully, it’s possible to fix the error by mounting the Windows image from the ISO, copying the necessary files, and then re-enabling the recovery agent:

1. Download a Windows 10 ISO file, and mount the ISO file to a drive.
2. Open Command Prompt as an administrator, and run the command: reagentc /disable
3. Create a new directory to mount your Windows image. Use this command: md c:\WinMount
4. Execute the following command to mount the image:

   dism /mount-wim /wimfile:E:\Sources\install.wim /index:1 /mountdir:C:\WinMount /readonly

5. Copy the recovery files from the mounted image to your system. Use this command:

   xcopy C:\WinMount\Windows\System32\Recovery\*.* C:\Windows\System32\Recovery /h

6. Set the recovery image path using:

    reagentc /setreimage /path C:\Windows\System32\Recovery /target C:\Windows

Finally, re-enable the recovery agent: reagentc /enable

PowerShell script to fix 0x80070643 – ERROR_INSTALL_FAILURE

If you do not want to go through the above steps, you can also use a PowerShell script to automate and update the Windows Recovery Environment (WinRE).

First of all, it is recommended to deploy the Safe OS Dynamic Update using the Microsoft Update Catalog, and finally run the PowerShell script by downloading it from our Discord server.

You’ll need to run the script with Administrator credentials in PowerShell on the affected devices. Thankfully, Microsoft says it’s investigating the reports, and it will soon publish a new emergency update.

It’s also worth noting that the issue was expected to occur on devices with low storage space for the recovery partition. Based on support documents, Microsoft increased the minimum free storage space requirements for WinRE in June 2023 without making changes to Windows Update.

As a result, when some people try to Windows 10 KB5034441 update, it fails with a vague error message like “0x80070643 – ERROR_INSTALL_FAILURE”.

The good news is Microsoft is working on fixing this and will have more information soon, but if you can’t wait, you can increase the size of WinRE.

The post How to fix Windows 10 KB5034441 failing to install with 0x80070643 error appeared first on Windows Latest

When Microsoft released Windows 10 version 19H2 in November 2019, the company said it would be a minor affair, but that wasn’t the case. This feature update dramatically changed the search bar in File Explorer by integrating OneDrive, which lets you directly view files from the cloud in the search results.

In other words, you also searched your OneDrive whenever you used the search box in the File Explorer. Before all this, the search bar was just part of the File Explorer. It showed your search results right there and allowed you to filter through them quickly. But then Microsoft decided to link it with web-based features, similar to the search bar in the taskbar.

This caused a severe performance downgrade, with our tests suggesting that some people may need to wait ages for the box to become responsive and quickly display the search result.

Some people continue to have problems with the search bar in File Explorer, with one user describing in a Feedback Hub post that “File Explorer window does not respond to the search bar. It accepts text but hitting enter on the keyboard doesn’t make it initiate the search, nor does clicking the magnifying glass”.

Windows 10 December 2023 Update turns off web integration in File Explorer

If you’ve just updated your Windows 10 with the December 2023 update (KB5033372), you might notice something different about your File Explorer.

As you can see in the above screenshot, the search bar at the top has returned to how it used to look before November 2019 – smaller and without the extra features like searching in Microsoft 365 or OneDrive.

Here’s the search bar before the December 2023 update:

Microsoft hasn’t documented the “downgrade” in its support document for the December or November 2023 update. However, my sources confirmed this change isn’t a mistake and could be related to the EU’s Digital Services Act, which sets specific privacy rules for tech companies.

The search bar is thinner, like before the Windows 10 19H2 update, and the quick, local search experience is back. But there’s a catch – the search bar doesn’t fit well with the other elements in the File Explorer on some configurations.

That’s because the other elements, like the address bar and buttons, are now larger than the search box. Some of you should be able to fix this by adjusting the display resolution or playing with the accessibility settings.

There’s a chance Microsoft may restore the web-based search box in File Explorer outside Europe in a future update.

If you prefer the slow and OneDrive-powered search box over the classic search, you can re-enable the cloud search using the third-party app “ViveTool“. You can open ViveTool via the command line, type vivetool /enable /id:18755234, and reboot the system.

Or you can uninstall the December 2023 update to return to the cloud-based search bar.

The post Microsoft reverts Windows 10’s File Explorer to pre-19H2 version, removes OneDrive search bar appeared first on Windows Latest

KB5033372 is a December 2023 Patch Tuesday update, and it will download or install automatically via Windows Update unless you manually pause it.

As mentioned above, today’s Windows 10 security update comes with a lot of new stuff, such as Microsoft Copilot, which is now pinned to the system tray. With Copilot on the taskbar, you can interact with Bing Chat or ChatGPT-based Copilot without opening Microsoft Edge.

Another notable change in KB5033372 is a larger news & interests feature panel. You’ll see the following patch when you check for updates:

2023-12 Cumulative Update for Windows 10 Version 22H2 for x86-based Systems (KB5033372)

Download Links for Windows 10 KB5033372

Windows 10 KB5033372 Direct Download Links: 64-bit and 32-bit (x86).

New features in KB5033372

Windows 10 is finally getting ‘Copilot in Windows’ feature, currently in preview. Positioned on the right side of the taskbar, this feature is designed for devices running Home or Pro editions.

This feature is basically Bing Chat running view Microsoft Edge WebView, and it can be disabled by right-clicking on the icon.

Starting with KB5033372, the news & interests feature on your device now boasts a larger display, making it easier for you to interact with and enjoy content that matters most to you on a grander scale.

For Home or Pro consumer devices and non-managed business devices, the update allows quicker access to the newest experiences. To enable this, navigate to Settings > Update & Security > Windows Update and enable the ‘Get the latest updates as soon as they are available’ option.

Here’s a list of all major improvements:

• The update resolves an issue leading to IE mode becoming unresponsive with multiple tabs open. Additionally, it enhances cursor performance in certain screen capture scenarios.
• An important fix addresses the absence of the touch keyboard during the out-of-box experience (OOBE), ensuring smoother setup and initial use.
• New functionalities affecting app defaults and pinning have been introduced, providing a more principled approach to these aspects in Windows.
• You will now receive opt-in notifications for Windows updates directly on the sign-in screen, promoting awareness and timely updates.
• The update addresses the manageability issue with the Trusted Sites Zone logon policy via mobile device management (MDM) and resolves a problem causing IE mode to become unresponsive under specific conditions.
• fontdrvhost.exe now remains responsive with Compact Font Format version 2 (CFF2) fonts. The update also tackles issues leading to reduced game performance and video stuttering for non-admin processes.
• The update enables the creation of cross-process windows while maintaining the use of out-of-process hosting for elements like WebView2, even under protected, top-level windows.
• Enhancements in this update support Conditional Access (CA) scenarios within Microsoft Defender for Endpoint.
• A localization fix has been made for Great Britain English (EN-GB) locales, correcting the error message for invalid characters in a new Windows Hello PIN.

Likewise, Microsoft has also patched a leak in volatile notifications, which previously could hinder signing in to the machine.

An issue with the Windows LAPS PasswordExpirationProtectionEnabled policy, which failed to activate the setting, has been addressed as well.

The post Windows 10 KB5033372 released with Copilot appeared first on Windows Latest

KB5032278 is an optional update, so it won’t download or install unless you manually head to Settings and click “Download and install”. Installing the November 2023 Update will bump Windows 10 22H2 to Build 19045.3758, and all the fixes or new features in the update will automatically ship with December 2023 Patch Tuesday.

The biggest change in the Windows 10 November 2023 optional update is support for an early preview of Microsoft Copilot, which lets you access ChatGPT and Bing Chat AI without opening your browser. Microsoft is also increasing the “News and Interests” window size to house more items.

The patch is titled “2023-11 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5032278)” and it can be downloaded by heading to Settings > Update & Security > Windows Update > Check for updates, and finally click “Download and install”.

You can also select “View all optional updates” to manage available patches or drivers.

Download Links for Windows 10 KB5032278

Windows 10 KB5032278 Direct Download Links: 64-bit and 32-bit (x86).

Windows 10 KB5032278 (Build 19045.3758) Full Changelog

After updating to Windows 10 Build 19045.3636, you will notice a new colourful Copilot icon button next to the Action Center icon on the taskbar.

This new button opens the Bing Chat AI in a Microsoft Edge-powered WebView, letting you interact directly with ChatGPT-like features on the desktop. But there’s a catch – Copilot on Windows 10 lacks support for native APIs, so you won’t be able to open apps or change settings as you can in Windows 10.

Also, installing KB5032278 doesn’t guarantee access to Copilot. Microsoft told us Copilot is available in select regions only, such as the United States, United Kingdom, and some Asian countries. If you’re in Europe or Asia and do not see Copilot, try changing your region.

There are other requirements to use Copilot on Windows 10:

• Windows 10 Home and Pro editions.
• 4GB of RAM and 720p resolution.

Our tests showed that Copilot in Windows 10 isn’t as impressive as its Windows 11 counterpart. If you aren’t a big fan of AI, you can always right-click the Copilot icon and hide the feature on the taskbar, reverting to the original look.

In addition to Copilot, Windows 10’s November 2023 update makes the news & interests feature a bit larger.

Similarly, several important bug fixes include fixing an issue that causes mouse movement lags and Internet Explorer mode crashes.

The post Windows 10 KB5032278 is out with Windows Copilot appeared first on Windows Latest

Found under Group Policy, you can now enable getting the latest optional updates on Windows 10 too. This feature was already present on Windows 11, and now the older OS is getting it too. Whether this feature will impact users or not, only time will tell.

As Microsoft confirmed earlier this month, you can try the new optional after installing the November 2023 optional update or December Patch Tuesday.  The IT admins can enable or disable this change as a Group Policy Object or a Configuration Service Provider policy for users.

For those unaware, optional updates often contain important fixes and improvements; we don’t recommend our users install them. There are some times when they become necessary. Suppose you are facing a rare device-breaking bug; there’s a good chance the optional update fixes it.

It’s best to read the changelog before installing the update and look at our articles to see if others have any issues.

If you still want to enable automatic optional updates, open Group Policy Editor in Windows 10 Pro or Enterprise and look for “Enable optional updates”.

In the “Enable optional updates” policy pop-up, you can toggle between the following options:

• Automatically receive optional updates (including CFRs). This lets you get all the new features and improvements. For example, if you use this policy, Copilot will automatically get enabled on Windows 10.
• Automatically receive optional updates. This option for devices lets you try next month’s Patch Tuesday update in advance.

Copilot is now available on Windows 10

As reported by us, Microsoft added its AI-powered assistant Copilot to Windows 10 last week. The assistant is available to users on the Release Preview Insider ring, and we expect it to roll out to everyone in the coming weeks.

Copilot will only be available to Home and Pro versions on Windows 10, with Education and Enterprise users getting them later. Users wanting to try Copilot should enable the “Get the latest updates as soon as they’re available” toggle in Settings and check for updates.

As per Microsoft’s Tech Community Blog, many features of Copilot will remain exclusive to Windows 11.

This further cements our belief that Windows 10 support won’t be extended beyond 2025. Users must update to Windows 11 to use Copilot in all its glory.

The post You can now enable automatic optional updates on Windows 10 appeared first on Windows Latest

In an update to the support document, Microsoft has confirmed Windows 11-like Copilot is coming to Windows 10 in the coming weeks. That’s because the tech giant is hearing ‘great feedback’ on Copilot in Windows 11 and wants to expand “that value to more people”, which is why AI is coming to Windows 10.

You need to know a few things before enabling Copilot. First and foremost, Microsoft previously told us that Copilot works in select regions only, and most European countries are not supported. Additionally, Microsoft has confirmed Copilot will only appear on PCs with 4GB RAM and 720p plus screen resolution.

How to enable Copilot on Windows 10

To enable Copilot on Windows 10, follow these steps:

1. Your device must be running Windows 10 Build 19045.3754 or newer. To get this particular update, Microsoft says users need to grab KB5032278 by joining the Release Preview Channel (this update will go live as an optional preview in the production later this month). Or you can find the .msu package on our Discord server.
   
2. Go to Settings > System > About and ensure the Build number is 19045.3754 or greater.
   
3. Download the open-source app ViveTool from Github and extract it to your downloads folder. This app, created by Albacore, lets you enable experimental but hidden features on your Windows device.
   
4. As shown in the above screenshot, open Command Prompt with administrative privileges and navigate to the location where ViveTool is extracted.
   
5. In the Command Prompt (admin) window, copy, paste and run the following command:

   vivetool /enable /id:46686174,47530616,44755019

6. Reboot your system.
7. If you do not see Copilot, right-click anywhere on the taskbar and select the “Show Copilot (preview) button.” The Copilot icon will then automatically get pinned to the right side of the taskbar.

As you can see in the above screenshot, the Copilot button is on the right side of the Windows taskbar, between the Action Center and Show Desktop buttons.

You can right-click the taskbar again if you want to hide the AI button from the right-click menu, but if you do not see the option at all, you will need to make one minor edit to the Registry.

In the Registry Editor, go to HKCU\SOFTWARE\Microsoft\Windows\Shell\Copilot\BingChat\ set “IsUserEligible” to 1, and save the changes.

Windows Copilot is limited, but it’ll eventually get there

As detailed in our Windows 10 Copilot hands-on review, several limitations are plaguing the AI experience, including the inability to interact with OS-level features. For example, you cannot open apps like Settings using the Copilot.

While this could change in future, Copilot on Windows 10 is currently Bing Chat running via Edge WebView.

Microsoft has also warned the feature may not be available on devices with compatibility issues, including devices with an incompatible app.

At some point in future, Copilot will be enabled on all PCs by default with more features.

The post How to enable Microsoft Copilot on Windows 10 appeared first on Windows Latest