#Solitaire plus for windows repair kit how to#
#Solitaire plus for windows repair kit drivers#
#Solitaire plus for windows repair kit update#
#Solitaire plus for windows repair kit driver#

Outdated chipset driver – Another indirect cause that might be a potential cause of these unexpected system crashes is an outdated chipset driver.In this case, the only viable fix is to uninstall the conflicting software (there might be other similar VPN tools that will produce the same behavior on Windows 11). NordVPN incompatibility – If you have NordVPN installed and configured to open every time you boot up your Windows 11 computer, keep in mind that this unexpected system interrupts can be caused by an incompatibility between NordVPN and a kernel sub-process.

#Solitaire plus for windows repair kit drivers#

You can typically resolve these by running the Hardware and Devices TroubleShooter and applying the recommended fix to enable your PC’s ability to auto-update with the newest drivers on all devices that are just connected. This issue is mostly reported to occur with new external drives that are just connected to a Windows 11 computer.

Common hardware inconsistency – It’s not uncommon to start facing this issue immediately after you connect a new peripheral.

Some users that we’re experiencing crashes with the LiveKernelEvent 193 error have confirmed that the issue was resolved completely after they’ve updated their Intel Wi-Fi driver with the latest compatible iteration.

Outdated or corrupted Intel Wi-Fi Driver – One of the most common causes that might be behind this behavior is an inconsistency with the dual-band wireless driver.

In the case where you would want to adjust the whitelist defined in the script, for various reasons, use the sample script below for AppX provisioning packages that will be removed by default when running this script using the embedded list. Manually validate what will be removed by the script

#Solitaire plus for windows repair kit update#

Create a PowerShell Script object, point towards the script and ensure it’s running in a 64-bit process in the System context, similar to the following configuration: What’s removed from the device after running this scriptĪs for built-in appx provisioning packages, here’s the list of apps that will be removed:Īnd for the Feature on Demand V2 packages, these will be removed:Īs always, you can update the $WhiteListOnDemand and $WhiteListedApps variables to include more apps, ensuring they’re kept on the device, or of course remove entries from both if you think the already added apps does not fit in your environment.

Remove Built-in apps for Windows 10 version 1903 – MSEndpointMgrĪs for Windows Autopilot and Intune, I’ve not written any posts as of yet, however the instructions are extremely simply. Remove Built-in apps when creating a Windows 10 reference image – MSEndpointMgr ConfigMgr, see the following posts for implementation guidance:

Notepad|MSPaint|PowerShell.ISE|ShellComponentsĪs for using the script when creating a reference image for e.g.

Windows 10 version 20H2: Added to the white list, but also extended the Feature on Demand V2 white list to include the following packages:.

Windows 10 version 2004 (20H1): Added Microsoft.VCLibs.140.00 to the white list.

I’ve made the script available on our GitHub repository along with all the other scripts that we’ve shared, and it’s available on the following URL: This script also works for when provisioning new devices using Windows Autopilot for devices to be managed with Microsoft Intune. Recently however, Windows Autopilot has increased in popularity. Originally, this method was developed for when creating a reference image here, as shown in the blog post below. Up until now though, I’ve been behind on keeping it up-to-date, but rest assured, here’s the latest version that now supports Windows 10 version 20H2 and below. During this time, I’ve attempted to keep my script updated after each new release of Windows 10.

#Solitaire plus for windows repair kit how to#

Over the years, the community has provided several solutions on how to accomplish this including myself. Since the release of Windows 10, it has been common for organization to try and reduce the footprint of built-in apps (or default apps) in their reference images, or even during bare-metal deployment.