Removing BEEP when adjusting volume in Windows

Windows 11 has been rolling out for a while now so many PC users ask the question is it wise and good to upgrade your Operating System to the latest Microsoft incarnation. No Thank you for reading, cya tomorrow in next article. Jokes aside, I truly believe that choosing to upgrade your System to Windows 11 at this point in time is a bad decision and I will explain why I do believe it.

Reasons to upgrade to the new OS

First of all, let me say what is good in Windows 11 and provide reasons why you should upgrade your computer.

1. The new fancy look made for modern computers. New Windows new look, Microsoft has tried their best to bring a new modern look to its flagship operating system and I must say that they have managed it. I could argue that it is a little bit late since Apple had this kind of look in years but hey, better late than never I guess.
2. Increased security This point is very valid but it will play a role only if you have all system requirements including TPM 2.0. If that is the case new security features of OS are really well done and are perhaps one thing that might nudge some people in installing W11 on their system.
3. New settings app The New and redesigned settings app inside Windows 11 is really great and it provides a great workflow and easy management of system settings. This is not some radical change but it will save time and make life much easier.
4. It is better suited to the newest hardware Windows 11 was made with the newest hardware in mind and its performances on it are great so if you are punching the latest tech this reason is sufficient to make a switch, however, if you are still on an older system you will not gain much by switching.

Reasons to avoid Windows 11 for now

1. Almost just a visual update to Windows 10 Some features of Windows 11 are great but they are not plenty of them to justify a new number and new version of OS. Considering what we really got new under the hood Windows 11 could have been just a patch and update to Windows 10 since the architecture is the same.
2. Bugs Each day there are new bugs reporting for Windows 11, most of them are at the moment unsolvable and are caused because hardware manufacturers' drivers and software overall is not W11 ready. This hinders the stability of some systems and introduces headaches to others.
3. Runs poorly on unsupported hardware Strange behavior has been reported on some older systems, granted systems are not officially supported but the point is OS is simply not working at the top of its game on older hardware.
4. No updates on non supported systems Officially stated if you install Windows 11 on non-supported hardware you will not get any security updated on in. This is a deal-breaker as far as I am concerned.
5. It is still under development When Windows 11 was released, Android native apps were not working on it, it later came with an update, this is just one example but there are more features that were promised but are not delivered on release and constant updates are fixing these things. It is obvious that Windows 11 is still under active development and not the final product that was promised.
6. Microsoft’s edge pushing And not just edge, some other things as well but most notably is edge pushing to borders they are risking lawsuit similar as they did in the past pushing and disabling any other browser except internet explorer.

Conclusion

Firstly I want to point that this is my personal opinion but going through facts and taking into account the current state of Windows 11, at this point, it is not worth making a switch. I am sure that in time it will become a system that will be worth upgrading to but until that time comes, my advice would be to stay with Windows 10.

Hello everyone and welcome to another great tutorial from errortools.com I hope everyone is feeling great and that you are prepared to boost the performance of your computer. This time we will speed up Windows startup time and overall performance by eliminating startup programs that we don't need and do not use. Microsoft itself and some application developers tend to have some applications or some services always active and set to be loaded on Windows startup. If you want to change which of these applications are starting up with your Windows and change them, follow this easy guide and you will be speeding up your Windows in no time. First thing is to open a task manager, fastest and most direct way of doing this is with a keyboard combination of CTRL + SHIFT + ESC When Task Manager opens, click on the startup tab on top. Once you click on startup you will get a list of applications that are set to be started when Windows is booted. You can now click on the application and then click on disable on the bottom button, the application status will update in task manager to disabled and it will not be booted anymore when Windows starts. In this same manner, you can enable back some applications if you changed your mind about them. Please note that some applications are using some services and must have them running or they will not work properly. The best practice is to disable applications you are positive you will not use or use rarely so you do not want them to slow down Windows.

If you are using a couple of graphics-intensive applications like video rendering software or some games, then something in the background of the system could get messed up and you might encounter the “LoadLibrary failed with error 1114, A dynamic link library (DLL) initialization routine failed” error message. This kind of error can usually get fixed by twerking some graphic settings, fixing and updating the drivers, and allowing your PC to work by leveraging the maximum use of the resources it’s got. Thus, in this post, you will be guided on some measures you can apply to resolve this kind of error message as soon as possible. Before you go over the options given below, if you have made any changes to any software component in your computer or installed new software recently, then you might want to undo them and then check if it fixes the “LoadLibrary failed with error 1114 “ error. Once you have that covered but you’re still getting the error, use the options given below as a reference to fix the error.

Option 1 – Try to modify the Dynamic Graphics Settings

You might want to modify the Dynamic Graphics Settings in order to fix the error. To do so, follow the steps below.

• Open Control Panel and then Power Options.
• From there, click on the Change plan settings option for your chosen power plan.
• After that, click on Change advanced power settings.
• Then look for the Switchable Dynamic Graphics option and then click on it to expand it.
• Afterward, expand the Global Settings option and then select Maximize Performance for both the “On battery” and “Plugged in” options.
• Now click on the Apply button and then OK to save the changes made.

Note: If the Switchable Dynamic Graphics option is not available on your computer, you can try the next given option below.

Option 2 – Try switching the Graphics card to High-Performance mode

Note that this second option varies from computer to computer since most computers use the Graphics card made by NVIDIA, while some by AMD and others use Intel HD Graphics. Thus, depending on which graphics card your computer uses, pick one of the three fixes below.

NVIDIA Graphics Drivers:

If your computer uses a graphics card made by NVIDIA and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop and then click on the NVIDIA Control Panel.
• After that, expand the 3D Settings on the left-hand side tree-structured list and then click on Manage 3D Settings.
• Next, select your preferred GPU on the right-side panel and then set it to the High-Performance NVIDIA Card from the drop-down menu.
• As an alternative, you can also go to the Program Settings tab,
• From there, select the program that you are trying to run from the drop-down menu and click on Add.
• Now set the graphics processor to a High-performing processor and then restart your computer to apply the changes made.

AMD Graphics card:

If your computer uses a graphics card made by AMD and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop.
• Click on AMD Control or Configure Switchable Graphics.
• Next, click on Browse and select the program where you encounter the error.
• Finally, click on High Performance for the selected program and then restart your computer to successfully apply the changes made.

Intel HD graphics:

If your computer uses the Intel HD graphics and then its drivers are properly installed and updated, then follow these steps:

• Right-click on any empty space on your desktop and then click on the Intel Graphics Settings.
• Next, click on the Power menu.
• After that, select a Graphics Power Plan for both the “On battery” and “Plugged in” options to High-Performance Power Plan.
• Then click on the Apply button and restart your computer.

I do not know about you, but I prefer to set my Windows to be more to my liking and not how Microsoft thinks it should be. Let’s face it, not all users feel comfortable whit Microsoft settings and idea how things should be. One of the things I particularly did not like even in Windows 10 is icons that come by default on my taskbar, now so far, well until the latest Windows 11 update you could remove default taskbar icons the same way as in Windows 10, just right-click on them and unpin, sadly with latest update build on Windows 11 this option has been removed. In order to remove default icons from the taskbar, one must go now to Windows 11 settings and choose from there which one you would like to be placed on it. Of course, this is nothing game-breaking but it still feels strange why the standard option has been removed, it just makes no sense but lately not many things that come from Microsoft do. I do not know about you, but I prefer to set my Windows to be more to my liking and not how Microsoft thinks it should be. Let’s face it, not all users feel comfortable whit Microsoft settings and idea how things should be. One of the things I particularly did not like even in Windows 10 is icons that come by default on my taskbar, now so far, well until the latest Windows 11 update you could remove default taskbar icons the same way as in Windows 10, just right-click on them and unpin, sadly with latest update build on Windows 11 this option has been removed. In order to remove default icons from the taskbar, one must go now to Windows 11 settings and choose from there which one you would like to be placed on it. Of course, this is nothing game-breaking but it still feels strange why the standard option has been removed, it just makes no sense but lately not many things that come from Microsoft do.

As you know, Windows PowerShell is a useful command-line utility in Windows 10 that can be used to manage the Local Users and Groups which affirms the multiuser operating system principle of Windows 10. Although there are other GUI-based utilities used to manage the Local Users and Groups, there are some system administrators that would still like to use the command-line utility to manage these Local Users and Groups. So in this post, you will be guided on how exactly you can manage the Local Users and Groups using PowerShell on your Windows 10 computer. To get started, refer to the options provided below to manage both the Local Users and Groups using Windows PowerShell.

Option 1 – Manage the Local Users via Windows PowerShell

• You need to first open Windows PowerShell as an admin. To do that, just tap the Win + X keys and select the Windows PowerShell (Admin) option.
• After opening PowerShell, you need to execute the “Get-LocalUser” cmdlet so that you can find all the details about all the local user accounts in your computer which would include the Account Name, Enabled status, as well as description.

Note: On the other hand, you can also get the customized data about several objects that are related to your account. For instance, if you want to check when was the last time the Local account’s password was set, then you need to execute the “Get-LocalUser -Name root | Select-Object PasswordLastSet” cmdlet. Thus, the structure for this cmdlet is “Get-LocalUser -Name root | Select-Object *”. Here are the objects you can use to get different sorts of data:

• AccountExpires
• Description
• Enabled : True
• FullName
• PasswordChangeableDate
• PasswordExpires
• UserMayChangePassword
• PasswordRequired
• PasswordLastSet
• LastLogon
• Name
• SID
• PrincipalSource
• ObjectClass

Option 2 – Manage the Local User Groups using Windows PowerShell

• Like what you did earlier, open Windows PowerShell as admin and then execute the “Get-LocalGroup” cmdlet so you can get all the information about all the groups of all the local user accounts.
• Now if you want to create a new Local User Group, just execute the “New-LocalGroup -Name <NAME OF THE GROUP> -Description '<ENTER THE DESCRIPTION OF THE GROUP HERE>'” cmdlet.
• And if you want to add Local User Accounts to a specific group, just execute the “Add-LocalGroupMember -Group '<NAME OF THE GROUP' -Member ('NAME 1','NAME 2','<ROLE>') -Verbose” cmdlet. You could also use the “Get-Localuser -Name john | Add-LocalGroupMember -Group '<NAME OF THE GROUP>'” cmdlet for the same purpose.
• If you want to display all the User Accounts of a specific group, just use the “Get-LocalGroupMember –Group ‘ ’” cmdlet.
• Now if you want to remove a local user account from a group, all you have to do is use the “Remove-LocalGroupMember -Group '<NAME OF THE GROUP>' –Member <NAME OF THE LOCAL USER ACCOUNT>” cmdlet.

The Clear Linux Project creates an operating system and software stack that offers highly optimized performance, security, versatility, and manageability. Clearly optimized for Intel CPUs and based on GNOME it will offer you incredible speeds if you are on Intel CPU. The big news, though, is that Clear Linux sports the shiny new Gnome 40. This is a fresher Gnome than you'll find even on Ubuntu's more experimental 21.04 release. The only big names that let you test drive Gnome 40 are Fedora and Arch Linux.

Packages only when you need them

Installation of packages is used by Swupd, a Clear Linux* package management tool. It is easy to use and pretty straightforward.

• "bundle-list" for showing what's installed
• "bundle-info" for details on installed bundles (such as owned files via the "‑‑files" flag)
• "search" for repository searching
• "bundle-add" for installation
• "bundle-remove" for uninstallation

The only problem here is the packages themselves. Clean Linux* has been imagined as a developer distro focusing mostly on well-development tolls. In intel’s words: “A Linux OS built for Linux developers”, so some things will be left out. Strangely enough some things as FFmpeg which if you want to have and blast some youtube videos while you work will have to complete manually by yourself.

Clear Linux* modular philosophy

Everything in Clear Linux* is based on a modular philosophy approach. There is no /etc/fstab file, the /boot directory is totally empty. Every partition to be mounted is enabled as a systemd "mount unit." Intel reaping the benefits of systemd's modular philosophy, where everything is a unit. If you know your way around systemd, intermediate-level configuration tasks should be straightforward. Any advanced configuration likely demands deep systemd knowledge.

Clear Linux* performance

As stated earlier this is Intel’s distro, optimized for Intel hardware meaning that Intel as the developer has every possible tool at its disposal to make use of hardware to its maximum potential and it shows. Distro almost leaves other ones two times in speed performance. So if you are looking for a distribution that will deliver you speed and it is aimed for developer Clear Linux* is for you.

Conclusion

Clear Linux* is a really interesting distro and seeing how Intel is adding new software packages on its official website it might have a bright future. But as always, be the judge for yourself and see if it can fit your needs. Go get it at: https://clearlinux.org/

If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.

Option 1 – Try to rollback, update, or disable the Graphics card drivers

Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Run System File Checker at boot time

• Once you get to the Welcome Screen part, click on Next.
• Afterward, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
• Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• After that, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 5 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.

Option 6 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:

• Tap the Win + R keys to launch the Run dialog box.
• Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
• Now click on the entries of every faulty driver and click on the Uninstall option.
• Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

The Windows 10 Telemetry and Data Collection features are auto-enabled and they collect all sorts of user activity and sends it to Microsoft. Microsoft says that the data collected only enhances the overall user experience and Windows functionality better but the number of data breaches happening across the globe has forced users to be extra cautious about their data privacy. So naturally, from stronger passwords and other services management, it is only logical to turn off Windows data gathering. To do so:

• Press ⊞ WINDOWS + R to open the run dialog.
• In the Run dialog type: taskschd.msc
• Press CTRL + SHIFT + ENTER key combo to open Task Scheduler in admin mode.
• On the left pane, navigate to the: Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program
• At the location, on the middle pane, right-click on the task named Consolidator and select Disable from the context menu...
• Repeat the process with all other tasks listed in the middle pane.
• Exit Task Scheduler.

What is 0x3D55? As you know, Windows 10 is loaded with various Universal Windows Platform or UWP apps such as the Microsoft News, Weather, Calculator, Windows Mail, and many other applications that are based on the modern UWP platform of Microsoft that was introduced in Windows 10. Each one of these apps has a shared piece of code in the kernel for them to be able to get executed across any device that runs the Windows 10 OS which includes laptops, PCs, 2-in-1 devices, mobile phones, mixed reality headsets, and many more. However, there are times when the runtime information for these apps ends up getting corrupted which causes them not to function as expected and throws errors like the error 0x3D55. This kind of error can be pinned down when the UWP app malfunctions and you can also find an error message in the Event Log that reads, “0x3D55: Package family <App name with ID> runtime information is corrupted”. So if you encounter this error, read on for this post will walk you through fixing it. There are three suggestions you need to check out to fix this error – first, you can try to reset the Microsoft Store cache, second, you can try to re-register or reinstall the problematic app and lastly, run the Windows Store App troubleshooter.

Option 1 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 2 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x3D55. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 3 – Try to re-register the UWP app via PowerShell

• First, type “command prompt” in the Start Search and right-click on Command Prompt and then select the “Run as administrator” option.
• Next, navigate to this location in the command line utility: C:/Users/<Insert Username>/AppData/Local/Packages
• After that, execute the “DIR” command to view the list of all the directories in the given location.
• Once the list appears, look for the ID of the problematic app and take note of it.
• Now tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.<YOUR APP ID HERE>).InstallLocation + 'AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

• Wait for the process to be completed and then restart your computer.

The Boot Configuration Data or BCD files have the instructions required by the Windows operating system in order to properly boot the computer. So if you experience any trouble when you boot your computer, then it is possible that it is due to some misconfiguration or even corrupted Boot Configuration Data files. And if you also encounter an error saying,

“The boot configuration data store could not be opened”

while you try to carry out any command on the bcedit.exe, then you’ve come to the right place as this post will guide you on how you can fix this error in Windows 10. This kind of error could pop up if the system is not able to locate the specified file. It is also possible that the requested system device can’t be found or that the boot configuration data store could not be opened. In addition, when you open the System Configuration or MSConfig, you might notice that there is no Boot data, and according to the reports, is that when you try to dual boot the computer, the installer will replace the default bootloader.

Explanation

In case you don’t know, Windows’ earlier versions were stored in the “Boot.ini” file. You can find the entry in the EFI firmware boot manager of the EFI-based operating system which is located at EFIMicrosoftBootBootmgfw.efi. Whatever the cause of the error is, there are several suggestions you can check out to resolve the problem. You can try to set an entry option value in BCD or enable the Advanced options menu, as well as rebuild the BCD. Before you proceed with the troubleshooting options provided below, make sure that you boot your computer into the Advanced Recovery Mode first since that’s where you can find Command Prompt under the Advanced Options. In addition, you also have to suspend or disable BitLocker and Secure Boot on your PC.

Option 1 – Try to set an entry option value in BCD

• Once you’re in the Advanced Options, select Command Prompt.
• Next, execute this command to set an entry point: bcdedit /set {current} Description "TheNameYouWant"
• After the command has been executed, it will enable the system to trust a version of Windows that is not trusted by default. This should fix the problem, if not, follow the next given options below.

Option 2 – Try to specify the BCD file

• In the elevated Command Prompt, execute this command: bcdedit /store c:BootBCD
• Once done, the command will give you a list of options and then execute this next command: bcdedit /store c:BootBCD /set bootmenupolicy legacy
• After that, restart your computer and select your Windows and then tap the F8 key right away.

Note: When you select the legacy option, the Advanced Options menu will be available during the computer boot up and then you can select into which operating system you can boot your computer into.

Option 3 – Try to rebuild the BCD files

The first thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.