Fixing Error 0xC1900208, 0x4000C in Windows

Typical use of file explorer will probably not need any kind of elevated privileges, but from time to time you might encounter some tasks that will require administrator rights in order to perform them. If this is the case you will need to run file explorer with these rights but inside Windows 11 that is somewhat hidden and not 1 click away. How this is the case we have decided to put a little tutorial on how to accomplish this very task and run file explorer with administrator privileges.

Open File Explorer via EXE file

1. Open File Explorer typically
2. Navigate to This PC > Windows (C:) > Windows
3. Locate file explorer application
4. Right-click on it and select Run as Administrator
5. Run File Explorer

A new instance of file explorer will pop with elevated administrator privileges.

Run it as an administrator using the Task Manager

1. Open the Task Manager ( CTRL + SHIFT + ESC )
2. Click on More details (at the bottom)
3. After the task manager expands click on the File tab
4. Click on Run New Task
5. Type in explorer.exe and check the box next to it that says Create this task with administrative privileges
6. Click on OK

File Explorer will now run as administrator.

Recently Logitech has released a new line of ergonomic mouse products on market, strangely shaped and lifted on a vertical axis Logitech claims that these devices will fix your issues and ease your hand pains for prolonged use of the computer.

The first time I saw this mouse I was not really impressed with its looks and somehow I thought it will not feel good. This all changed when I actually started using it, surprisingly altho strange in looks it does feel much more natural and much less stressful on hand. Also, it felt like I have used it before, personally, I did not need any adjustment period in order to use it fully.

All of that being said I will admit that using it for gaming is still not an option for me, someone might find it ok, especially if they play some games that do not need to be responsive like strategies or similar but for RTS and FPS I will still stick to the typically shaped mouse. This might be just a habit for me but somehow I feel more responsive with the typical mouse, but for anything else, this is the mouse that will keep your hands stress-free.

Now in order to get the mouse to be really recommended it needs to have some good technical specifications as well, looks are not all. The less important detail is that the mouse comes in 3 different colors: Black, white and pink, and its technical specifications are:

Specs & Details

Dimensions

Height: 71 mmWidth: 70 mmDepth: 108 mmWeight: 125 g

Technical Specifications

Sensor technology

• Sensor type: Logitech Advanced Optical Tracking
• Dpi range: 400-4000 dpi (Fully adjustable with 100DPI increments)
• Nominal value: 1000 dpi

Buttons

• Number of buttons: 6 (Left/Right-click, Back/Forward, Middle button, Scroll-wheel with a middle click)

Battery

• Battery type: 1x AA battery (included)
• Battery life: up to 24- months Battery life may vary based on user and computing conditions.

Connection type support

• Logi Bolt USB receiver (included)
• Bluetooth® Low Energy Technology

Wireless range

• 10-m wireless range

Personally, I would recommend this mouse for anyone who does work in front of the computer during the whole workday since it really does loosen grip and strain on hands.

Error Code 707 - What is it?

Error code 707 is a typical Gmail error. Gmail is an email service provided by the largest internet giant Google Inc. It is an email service that is most widely used by web-based email providers with more than 425 million active users worldwide. The error code 707 is usually displayed in any one of the following formats:

“Oops... the system encountered a problem (#707)” “Server error occurred and your email was not sent (error 707)”

Solution

Error Causes

The error code 707 may be triggered due to many reasons. These include:

• Enabled Lab ‘Background Send’ feature on Gmail
• Web browser history and cache is full of junk content
• Outdated browser

Though this error code is not fatal it is advisable to fix it right away to avoid inconvenience and to ensure your email is sent right away without any delays.

Further Information and Manual Repair

Here are some of the easy DIY methods to repair and fix the error code 707 on your PC. These methods are simple and do not require any kind of technical expertise. So, even if you are not technically sound, you can repair the error code 707 on your system in no time.

Method 1

Sometimes you may experience error code 707 while sending email via Gmail because of the enabled Background send labs feature. To fix this error here’s what you must do: Log in to your Gmail account, click on the Gear Box, and select settings. Now simply switch to the lab tab under the settings. Here search for Background Send. If you can’t locate it, then scroll down and insert background Send in the find box. Once you find this lab feature, disable it. After disabling this feature, try resending the email. Hopefully, this will resolve the issue. Nonetheless, if the error 707 still persists, then try method 2 given below.

Method 2

The error 707 may also be triggered if your web browser becomes outdated. If so, then it is advisable to update the browser to resolve the issue. Simply download the latest browser version from a reliable website. After the installation is complete, log on to your Gmail account and then try to send an email. If the email is sent successfully, then the issue is fixed.

Method 3

Try clearing cache and web browser history.  When the web browser history and cache are full of junk files, then you might experience this error on your system. Sometimes this can also lead to registry issues. To remove the error and repair the registry immediately, download Restoro. This is a multi-functional and user-friendly PC Fixer compatible with all Windows versions and embedded with multiple powerful scanners including a registry cleaner. It scans your entire PC for such errors. It clears the registry, removes all obsolete and unnecessary files including cookies, web browser history, junk files, and invalid entries, and cleans it right away thereby fixing the error immediately. Click here to download Restoro and resolve error code 707.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

Each time you open an application inside your Windows 11 operating system, it is opened with standard privileges. Now, please note that your account privileges and application privileges are two different things, you might be the administrator of the system but when you open the app, it still opens with standard privilege. Most of the time running applications with typical settings is fine but from time to time we might have some applications that will require running with administrator privilege in order to work properly. In this case, it is very easy to do it, you just right-click and choose run as administrator. Although a very easy solution, it can be quite annoying if running the app is on a daily basis or even more times per day. If this is the case then right-clicking and choosing to run as administrator can be a daunting task, sometimes you can even forget to run it like this in heat of work and some unforeseen consequences might occur. Luckily there is an easy hack so you can open the chosen application each time as an administrator with a simple double click each time.

Setting application to run as administrator always

1. Locate application executable file
2. Right-click on in and choose properties
3. Click on the Compatibility tab
4. Check the box next to Run this Program as an Administrator
5. Click on Apply
6. Click on OK

From now on each time you open an application normally with a double click, it will be opened as administrator privileges.

As you know, Windows programs depend on several operations to get executed and at the same time, there are also numerous parameters that have to be fulfilled for a program to get executed. However, based on some reports, there was an error when some users tried to run a program. This error says, “The application was unable to start correctly (0xc00007b)”. There could be various reasons why this error occurs but the main one is most likely due to an x86 application that is not compatible with the x64-based operating system. To fix this problem, you can run the Check Disk utility or reinstall the application or the Microsoft .NET Framework. You can also try reinstalling DirectX or replace the corrupted DLL file(s). For more details, refer to the given options below.

Option 1 – Try running the Check Disk utility

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 2 – Re-enable the Microsoft .NET Framework

You could also try to disable the Microsoft .NET Framework then enable the latest version of the .NET Framework on your PC and check if the error is fixed

Option 3 – Try to reinstall the program

There are times when some supporting module for your application under the hood could have messed up the application where you get the error. To fix this, you have to uninstall the program and then download its latest version from its official site and then install it again. Once you’re done, run the application and see if the error is fixed.

Option 4 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your computer.

Option 5 – Try running the DirectX Diagnostic Tool

Since the error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 6 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Recently, a lot of users experience issues after the Windows 10 v1903 upgrade and one of them is that the Cortana Web Preview is not functioning like it’s supposed to. Even though Microsoft has already replaced the unified search where you no longer have to use Cortana, it is still undeniably useful and is packed with some great features, one of which is the Web view. Each time you type a search query, it will open a web view where you can see the results using Bing. However, some users reported experiencing some issue wherein the web view does not show anything and appears to be broken and users have to click on the Open in Browser link. Thus, if you are one of the users who experience the same problem, then this post is for you – it will guide you on what you can do if the web preview in Cortana is not working on your Windows 10 device. To fix the Web Preview issue in Cortana, you can try to restart Cortana or reset it using the Windows Settings app or change the Search filter level. You could also try to run the Windows Store App troubleshooter or re-register or reinstall Cortana. For more details refer to the options provided below.

Option 1 – Try to restart the process of Cortana

There are times when the running process of Cortana might encounter an error and breaks a particular component of the whole service so the first thing you can do is to restart Cortana’s process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and look for Cortana’s entry.
• Once you find it, right-click on it and select the End task option.
• Afterward, open Cortana again and see if it fixes the web view problem or not.

Option 2 – Try changing the search filter level

The next thing you can do to fix the Web View is to change the search filter level. All you have to do is go to Settings > Search and change filter level and from there, modify the search filter level and then see if it fixes the problem.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the Web Preview problem in Cortana. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset Cortana via Settings

• Launch the Windows 10 Settings app and go to Apps > Apps & Features.
• Next, look for the entry of Cortana on the right-side panel and select it.
• After that, select the Advanced options and then select the Terminate button under the Terminate section.
• Once done, click on the Reset button under the Reset section.
• Restart your PC.
• After your computer boots, launch Cortana again and check.

Option 5 – Try to re-register and reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.

• First, right-click on the Start button and click on the Windows Powershell (Admin) option from the list.
• Next, type the following command and hit Enter to execute it:

Set-ExecutionPolicy Unrestricted

• After that, execute this second command to reinstall Cortana:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

• Restart your computer and check if the Web Preview in Cortana is now working.

As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few. Here are some of the common Blue Screen errors related to the Storport.sys file:

• KMODE_EXCEPTION_NOT_HANDLED
• KERNEL DATA INPAGE
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL
• SYSTEM SERVICE EXCEPTION

Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:

• “Improved performance, both in terms of throughput and the system resources that are utilized.
• Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”

If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:

• First, tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the Storport.sys Blue Screen error is to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. Option 2 – Try to recreate the Storport.sys file If the first option didn’t work, the next thing you can do is to recreate the Storport.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to Storport.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the Storport.sys Blue Screen error is now fixed.

Option 3 – Run System File Checker or SFC scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Reboot your PC.

Option 4 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.sys. 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.

There are times when it is really inevitable to delete your hard drive partitions especially if you are already running low on disk space in your Windows 10 computer. Users typically delete the volume which is not being used in such cases in order to free up some space for the volume that’s running low on disk space. To resolve the problem, users tend to use the Disk Management utility to delete hard drive partitions. However, some users reported that the “Delete volume” option is not available as it is grayed out. Thus, users aren’t able to delete hard drive partitions and aren’t able to free up disk space. This kind of problem usually occurs when there is a Page file on the volume that you are trying to delete and so on. Oftentimes, this issue is mistaken for the problem where you are unable to delete an EFI-protected partition. However, in this case, not only you are unable to delete EFI-protected partition but also NTFS file systems. This is really hard to deal with but worries not for there are some potential fixes you can check out to resolve this problem.

Option 1 – Try to manage the Page file in the Partition

As mentioned earlier, if a Page file exists in a partition, you won’t be able to delete it. The page file is what stores your data when the system’s random access memory fills up. To resolve this, follow these steps:

• Go to the Start menu and type “View advanced system settings” in the field and open it from the search results.
• Next, click on Settings in the Advanced tab.
• On the new window that pops up, go to the Advanced tab and select Change.
• Next, uncheck the checkbox of “Automatically manage paging file size for all drives” and highlight the drive you want to delete.
• Then select “No paging file” and click on Set.
• Now click on the Apply and OK buttons on all the windows and restart your computer.

Option 2 – Delete storage partition via Command Prompt

• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also type in “cmd” in the Cortana search box and right-click on the Command Prompt icon and then select the “Run as Administrator” option from the context menu.
• Once you have Command Prompt pulled up as admin, type in and enter this command – diskpart
• After entering this command, the Diskpart Utility will start. Diskpart Utility is a command-line-based utility just like Command Prompt but it will get a UAC Prompt after you invoke it so you have to click Yes for the UAC Prompt.
• After that, type in list volume and tap Enter to see the list of all the partitions created on your PC. This includes both types of partitions that are visible to the normal users in the File Explorer as well as the ones that are created by Windows 10 by default which helps it in storing the boot files and other essential system files.
• You should see a list of all the partitions made on your computer. Select the partition you want to delete by its Unique Identification number as Volume X where X denotes the Unique Identification Number.
• Next, type in the select volume number command and hit Enter to select the desired volume.
• Then delete the volume you’ve selected and type in the delete volume command and hit Enter to delete the volume you just selected and convert it into unallocated space.

Option 3 – Delete storage partition via Windows PowerShell

• Start by tapping the Win + X keys or simply right click on the Start button and select Windows PowerShell (Admin) or you could also type in “Windows PowerShell” in the Cortana search box and right-click on the Windows PowerShell icon and select the “Run as administrator” option.
• Once you’ve opened the Windows PowerShell, type in the Get-Volume command and hit Enter to get a list of all the partitions on your PC.
• Next, select the drive letter you want to delete and then type in the Remove-Partition –DriveLetter command and hit Enter to delete the selected partition. Note that you need to replace the drive letter with the letter of the partition you want to get rid of.
• After that, it will ask you for confirmation. Just hit the Y key for Yes or hit the A key to say Yes to All. This will delete all the partition you’ve selected and will move them in as unallocated space.

Error 103 - What is it?

The error 103 may occur either due to issues in your Google Chrome browser or system issues. If error 103 occurs when using Chrome, this means there is a conflict between Google Chrome and the antivirus program running on your PC. It is displayed in either of the following formats: ‘Chrome error 103 connection aborted’, ‘Chrome error 103 err_connection_aborted’ or ‘Error 103 (net: ERR_CONNECTION_ABORTED): Unknown error. However, if this is a system error code, it may be displayed in the following format ‘The semaphore cannot be set again’ or as ‘ERROR_TOO_MANY_SEM_REQUESTS’ or as the value 0x67.

Solution

Error Causes

The error 103 is triggered due to multiple reasons such as: The conflict between Google Chrome and anti-viruses arises because when the web browser attempts to update, the anti-virus programs on your PC may view the update as a threat. Due to this, the connection to the internet is terminated and the error 103 message is displayed on your computer screen. And besides, this keeps you from upgrading your Google Chrome browser too. Other causes include:

• Viral infection
• Missing Windows component called ‘expand.exe’
• Registry overlaps
• Incompatible drivers

Further Information and Manual Repair

Here are some of the easy and efficient ways to resolve error 103. Choose a method according to the error 103 messages displayed on your screen.

Method 1: Check for the ‘Expand.exe’ Windows component

This method is workable if the error 103 is triggered due to browser issues. To get started, follow these steps. First, go to the start menu, and in the search bar type ‘expand.exe’. If you are able to find it, move it to the following directory C:\Windows\system32. However, if you are unable to locate it, then copy the file from Windows installation CD. Once you copy the file to the directory, reinstall the updated version of Google Chrome.

Method 2: Change the Location of the Temporary File

If the error still persists, try method 2. Go to the start menu and open the Run window. Now type C: and press OK. Then go to File, then New, and then Folder. Now create a temporary folder and name it ‘test’. After that go back to the start menu and open the Run window again. Now enter the following text in the text field:cmd.exe then press OK. In the command prompt type set TMP=C:\test. After that try reinstalling Google Chrome by typing the following in the command prompt: start ChromeSetup.exe.

Method 3: Update Drivers

If the error message 103 is generated due to system issues, then try updating drivers. Sometimes the error may occur due to incompatible drivers.

Method 4: Perform an Entire PC Scan for Viruses

To resolve error 103, perform an entire PC Scan for viruses. Sometimes the error may occur due to viral infection. Removing viruses may fix the error.

Method 5: Clean and Restore the Registry

If the error is triggered due to registry issues, then it is advisable to download Restoro. This is a multi-functional PC repair tool integrated with powerful utilities including an anti-virus, a registry cleaner, Active X controls, and class scanner, and a system optimizer. The registry cleaner feature wipes out all the unnecessary files including cookies, junk files, and bad registry keys that corrupt the registry. It cleans and restores the registry instantly. The anti-feature removes all viruses and spyware while the system optimizer utility ensures your system works at its optimum speed. It can be downloaded on all Windows versions. It is safe and efficient. This software is a one-stop solution for all PC-related errors. Click here to download Restoro.