Fix Error Code 30088-26 in Windows 10

Sometimes, some applications after they are installed will put their shortcut in the context menu (right-click on desktop) for easy access, most of the time these are some system tied applications like AMD and Nvidia control panels or archives like WinRAR or 7ZIP but it can happen even for some usual application to do this.

There are some applications that you use frequently and they could be worth putting in the context menu, if you want to avoid clutter on the desktop or in the taskbar this is the third place that you should consider placing shortcuts.

Doing this will require some playing and tweaking in the Windows registry editor so be careful when editing the registry since bad entries can lead to system crash or instability. Follow step-by-step instructions.

Adding apps to the context menu in the registry

Creating entry

Open the registry editor by searching Regedit and pressing enter than inside of the registry editor search for the next key:

HKEY_CLASSES_ROOT\Directory\Background\shell

Select shell and right-click on it, hover over New and in the submenu click on Key. In the next step, you need to name a key, this name will be the thing that will be shown in the context menu when you right-click on a desktop so type in the name that you would like or the name of the application that you wish to add to the menu.

If you wish you can even add a keyboard shortcut to launch this specific application. To do this select entry that you have created and edit the default value, inside the edit string in the Value data field type first & and after that key that you would like as a shortcut. Now after right click if you hit your shortcut key app will be launched right away.

Adding command

The next task is to create a command key that will actually hold the command to launch the application. Right-click on the entry that you have created, hover over New, and click on Key.

Next, you’ll need to create the command key that will actually hold the command used to launch the application. Right-click on the new Notepad key, and then choose New \ Key from the menu. Name this key 'command', all in lower case and without hyphens.

Now in order to finish setting the launcher, you need the full path of the file that you would like to run. Locate your file in file explorer or in another tool and copy its path by SHIFT + right-clicking on the file itself and choosing copy as path option.

Now click on the command key and double click on the default key on right to edit it, inside the field value data paste your path to executable. close and save the registry and you are done.

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given options below.

Option 2 – Ensure that all the supporting processes and services are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 3 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox error.

Error Code 0x80070017- What is it?

Error Code 0x80070017 is an error code that is most often associated with Windows 10 installations, although it has also been encountered by users on previous versions of the Windows operating systems. It is usually encountered as users attempt to install a new version of the software on their machine.

Common symptoms include:

• A vague error message regarding the inability of the system to copy over the necessary files pops up as users attempt to install a new version of the Windows operating system on their computer

While it can be hard to tell what the exact cause of Error Code 0x80070017 is on your specific device, the good news is that there are two primary methods that can be used to fix the problem and to allow you to proceed with your installation. These two methods do require some degree of technical knowledge and/or skill, so if you don’t feel like you have the ability to undertake them on your own, be sure to get in touch with a trusted computer repair professional to assist you.

Solution

Error Causes

The most basic cause of Error Code 0x80070017 is that some of the files that are needed by the system to complete the installation are either not being found by the computer or are believed to be corrupted by the system. When this happens, security features within the software prevent it from completing the installation process, so as to avoid damage to the computer. Error Code 0x80070017 can be disruptive to your installation process, but there are two basic methods that can be employed to resolve it.

Further Information and Manual Repair

While it can be frustrating to encounter Error Code 0x80070017 on your Windows machine, there are two methods that can be used to try to resolve the problem. One of these methods is extremely simple, even for the most basic users, while the second method takes a little bit more skill and technical knowledge. If you aren’t able to complete these methods on your own, be sure to get in touch with a qualified computer repair technician that can assist you. Here are the best ways to attempt to resolve Error Code 0x80070017 on your device:

Method One:  Clean Your Physical Disk

If you purchased a physical disk version of the installation files for your Windows operating system, remove the disk from your drive and clean it using a microfiber or other lint-free cleaning cloth. As you wipe down the disk, do not use any chemicals, and be sure to wipe gently from the center towards the outside edge rather than the other direction, as failure to do so can damage the disk irreparably.

In some cases, you may need to contact Windows support if you believe that there is an error on the disk itself, such as a scratch, that would prevent the disk from being used as needed in the installation process. They may be able to offer you a replacement disk or you may be able to download a digital copy of the version that you are attempting to install on your machine.

Method Two:  Use the Chkdsk Utility

To determine if there may be an error within the disk drive itself, place the installation disk into the drive and restart the system. Go through the prompts until you see the option to “repair your computer.” Choose the operating system that you are using, go into the menu for System Recovery, and type in the words “Chkdsk/r” to begin to use the tool.

Whenever you run a tool like Chkdsk on your computer, it is important to restart your machine afterward to ensure that any changes that have been made are able to be fully applied and accepted by the operating system that you are running.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.

If you encounter the NMI_HARDWARE_FAILURE Blue Screen error while using your Windows 10 computer, then read on as this post will guide you in resolving this kind of Blue Screen of Death error. NMI HARDWARE FAILURE or “Non-Maskable Interrupt” Blue Screen error occurs when there is some hardware malfunction in your computer. When you encounter this Blue Screen error, you may get a stop code of 0x00000080 which can randomly occur while you use your computer. However, a lot of users reported encountering this error while they were trying to update or install their Graphics Card drivers. The stop code that you may get for this BSOD error is 0x00000080. The error can occur randomly during your usage of the computer – but a large number of users have reported this error while they are updating or installing their Graphics Card drivers. In this post, we will be covering all the possible fixes for this error. NMI_HARDWARE_FAILURE error on Windows The NMI_HARDWARE_FAILURE bug check has a value of 0x00000080. This bug check indicates that a hardware malfunction has occurred. There are various hardware malfunctions that can cause this kind of Blue Screen error. However, pinpointing the exact cause is quite difficult. Worry no more for the following fixes provided below can help you resolve the NMI_HARDWARE_FAILURE Blue Screen error no matter what the cause of the problem is.

Option 1 – 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 NMI_HARDWARE_FAILURE. 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 2 – Try to rollback, update, or disable the Graphics card drivers

Since the NMI_HARDWARE_FAILURE 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 3 – Make sure that all memory modules have the same type

This third option is quite technical and tricky. If you often use multiple physical RAMS on your Windows 10 computer, then you have to check first if they are of the same frequency. After that, the first thing you should verify is if the chip is properly compatible or not. And if the sockets are attached using some kind of adapter or non-recommended device, it could cause some issues while giving a performance hit to your computer.  If you were able to find such a setup, you have to undo it or install the proper and recommended as well as compatible hardware.

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 NMI_HARDWARE_FAILURE error. It can be found on 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.
• From there, 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.

Internal Error 2753 - What is it?

Internal error 2753 is associated with Windows Installer failure. The Windows Installer is basically an in-built software program in Windows 7 and 8. It installs all programs on the system smoothly, saves the program in the computer program files and in the Windows Registry. Though this can be carried manually Windows Installer makes the installation process much easier. However, internal error 2753 can cause a great deal of distress and frustration during program installation. This error prevents you from installing your desired program successfully.

Solution

Error Causes

The 2 known causes for Internal Error 2753 are:

• Viral infection
• Windows Installer not properly registered

Further Information and Manual Repair

To resolve internal error 2753 on your system, try the methods discussed below. These methods are easy and require no technical expertise. Let’s get started:

Method 1 - Remove All Malicious Programs

Malicious programs like viruses, malware, adware, Trojan and spyware can corrupt programs on your PC like Windows Installer. If this is the underlying cause of error code 2753, then simply download a powerful antivirus on your system. Run it to scan for all such malicious programs and remove them. Once your PC is clean, try installing your desired program. This will hopefully resolve the issue. If the error still pops up then try method 2.

Method 2 - Register Windows Installer Properly

To do this, go to the start menu and then open Run and type ‘cmd’ in the box, and press OK. This will open the DOS command window. In the command prompt type "regsvr32 vbscript.dll" and then press Enter to proceed. After that, you will see a message that will read as "DllRegisterServer in vbscript.dll succeeded." This means Window Installer files have been successfully registered on your PC.  Now you can try installing your desired program again. If the installation begins and completes successfully, then the error is resolved.

Method 3 - Undo Recent Changes

If nothing works, then use the Windows System Restore Utility tool to undo recent changes. This will bring back your PC in the former state before you experienced the error 2753 on your PC. To access System Restore Utility, press Start and type System Restore in the search box. Now follow the steps in the Wizard to choose a restore point. Once you select the point, reboot your system to activate changes.

The Windows 10 Orange Screen of Death, unlike Blue Screen of Errors, is quite an uncommon error where the hardware is the culprit which is mostly caused by some issues with the GPU. If you are currently facing this problem, then you’ve come to the right place as this post will guide you on what you can do to fix it. There have been reports from users that the Orange Screen of Death is caused by various reasons. Some users reported that they encountered Orange Screen of Death when they were watching a YouTube video, while some were not able to boot into their Windows 10 PCs and encountered an error instead of that either says, FAULTY_HARDWARE_CORRUPTED_PAGE or WHEA_UNCORRECTABLE_ERROR error. In addition, this error can also occur when your computer wakes up from Sleep or while using BitLocker, or while you use a second monitor. Whatever the case is, you can try updating your drivers or lower the clock speed of the GPU. You could also try to fix the DRIVER_IRQL issue in case it’s the one that triggers the error or performs Automatic Repair or uninstalls any recently installed software.

Option 1 – Update your Graphics card drivers

One of the possible reasons why you’re getting the Orange Screen of Death error is most likely related to the Graphics card drivers in your computer. Thus, the first thing you can do to resolve it is to update these drivers by following these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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 to uninstall software you’ve installed recently

If you have installed a software or two recently and then suddenly encounter this Orange Screen of Death, then they are most likely the culprits. The best thing you can do is to first check the System Log in the Event Viewer for any additional information in case it’s not the GPU but some other driver or device that’s causing the error. Once you have identified the culprits, uninstall them and see if the error is fixed.

Option 3 – Try disabling Overclocking

If overclocking is enabled, you might have to disable it as some users reported that the WHEA_UNCORRECTABLE_ERROR 0x00000124 error started to appear right after overclocking. To disable it, follow the steps below.

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the WHEA_UNCORRECTABLE_ERROR 0x00000124 error is now fixed.

Option 4 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the Wdf01000.sys Blue Screen error, you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 5 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

There are a lot of online services and a lot of ways to get your public IP address. One of them being typing whats my IP in Google search and you will get immediate results. But there is a way to get the same information inside Windows 10 which could be very useful if for any reason you can not connect to mentioned services. By checking public IP directly inside your windows you can make sure that the issue for not being able to open some websites is not due to your public IP. In order to use this Windows feature, we will be checking our public IP using Windows PowerShell. To open Power Shell in Windows first press ⊞ WINDOWS + R to open the run dialog Inside run dialog type Powershell and press ENTER In the Powershell type in the following command and press ENTER

(Invoke-WebRequest -uri "http://ifconfig.me/ip").Content

When the command finishes you will see what is your public IP address, if you wish to know more about your connection type in and press ENTER:

Invoke-RestMethod -Uri ('https://ipinfo.io/')

This command will provide you with further information like city, region, country, and others.

Originally Microsoft has imagined its widgets menu as Microsoft-only widgets but it seems that they have changed their mind. Due to the latest leak, it seems that Microsoft will open the widgets menu to 3^rd party developers as well but at launch, it will be only official widgets. It was hinted that later widgets menu will be open to developers who want to bring their own stuff into it. Distribution, date, and technology that will need to be used in order to create your widget have not been discussed nor leaked at a given time but in some way, I am very glad that at least some customization will be in Windows 11. It is funny and amusing how some things that were in Windows Vista are getting back like glass design, round corners, and widgets. Let’s just hope Windows 11 will be a better Windows than Vista was.

Microsoft starting as of today will block its Office 365 users if they are using Internet Explorer or early versions of Edge browsers. So if you are using older non Chromium Edge versions of Microsoft browsers you can no longer access Office services until you switch. Now normally I would fully support this kind of decision since Internet explorer is a slow and vulnerable browser and the edge is similar in that regard. The new edge browser is great and it should be used but the issue I have is that Office 365 is not free, it is a premium feature and I am wondering how Microsoft plans to deal with people that have already paid for service but suddenly cannot access it anymore.