The procedure entry point could not be located

There are times when you try to open a file, an executable file for instance, but were unable to do so since you encounter an error in an Open File – Security Warning dialog box that says, “This publisher has been blocked from running software on your machine, You must unblock this publisher to run this software”. This kind of error is most likely thrown by your operating system because it considers the file to be unsafe and could potentially harm your computer. However, if you’re certain that the file is harmless, read on as this post will walk you through fixing the error so you can open the file without getting an error. There are various options you can check out to fix the error. You may run the program using Command Prompt or unblock it using File Properties. You could also try turning off SmartScreen or use the unblock file command in Windows PowerShell.

Option 1 – Try running the program via Command Prompt

• Tap the Win + R keys to open the Run dialog box and type “cmd” in the field and hit Enter to open Command Prompt.
• Next, tap the Shift key and right-click on the program or the executable file, and then select the “Copy as path” option.
• After that, paste this path in the Command Prompt window and tap Enter to open the program.

Option 2 – Try to unblock the file using File Properties

• Right-click on the file you were trying to open and select Properties.
• Next, click the Unblock button and then click on the Apply and OK buttons.
• You should now be able to open or access the file without getting the error.

Option 3 – Turn off SmartScreen

The next thing you can do is to turn off SmartScreen temporarily. All you have to do is open the Windows Defender Security Center and from there, go to the App & browser control section. After that, click on the radio button for Off under Check apps and files. Once you’re done, try opening the file again. Don’t forget to enable the SmartScreen back on.

Option 4 – Try to use the Unblock-File command in PowerShell

You might also want to utilize the Unblock-File command in Windows PowerShell as it will unblock the file so you can open it. To execute this command, follow these steps:

• Tap the Win + X keys and then click on Windows PowerShell.
• After opening PowerShell, type or copy and paste this command and tap Enter to execute it: Get-ChildItem -Path 'C:Users<username>Downloads' | Unblock-File
• The command you entered will unblock all the files in the Downloads folder, assuming that’s where the file you were trying to open is stored. If it’s not, then replace the path with the path where the file is located. Take note to also replace “<username>” with your Username.
• Now check if the file has been unblocked by accessing or opening it.

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.

Default Taskbar inside Windows 11 is pretty good if we are talking about its height. Sitting at 48 pixels it is a pretty decent size considering functionality and size ratio but if you want to make it a little larger or smaller know that you can do that as well in order to customize it for your personal needs. Sadly in order to actually change height size, you will have to do it inside the registry editor, but worry not, we are here with you to guide you all the way, one step at a time. Also, note that you can only change Taskbar from normal size of 48px to either small of 32px or large gapping at 72px. Icons will also be scaled proportionally with the taskbar.

Guide

1. Press ⊞ WINDOWS + R to open the run dialog
2. Inside run dialog type in RegEdit and press ENTER
3. In registry editor locate and find HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
4. Right Click on it to select it and create a new DWORD (32-bit) value
5. Name the value TaskbarSi
6. Inside TaskbarSi double click in order to set the value to 0 if you want a small size Taskbar, 1 is if you want to revert back to medium (standard one), or type in 2 if you want a large Taskbar.
7. Save and close the Registry editor
8. Reboot PC

And there you go, you have successfully changed Taskbar size inside Windows 11. If you want to revert back to standard size just repeat steps and place 1 as a value in point 6.

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• 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, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. 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.
• 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 install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Configure 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 ntkrnlmp.exe 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 4 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ntkrnlmp.exe. 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.

As you know, Microsoft constantly releases new updates with the main goal of fixing bugs as well as deliver users with new and exciting features. However, there are times when the latest update comes with an unwanted bug. One of these bugs is an error message saying, “Low Disk Space. You are running out of disk space on Local Disk (G:). Click here to see if you can free space on this drive.” So if you have recently installed a Windows 10 update, then you’ll most likely see a completely new drive on your computer which will appear right after the installation of the update and you’ll also start seeing the aforementioned error message. It gets irritating as this error message keeps on popping up even if you still have a lot of free space on your other drivers. Obviously, the main reason why this error message pops up all the time is the bug brought along by the Windows Update. This bug unhides the recovery partition drive and allocates it a drive letter which is why you are seeing a new drive in your computer. Thus, you can get rid of the pesky error message by simply removing the letter of the new drive. Just remember that you must not delete anything from the recovery partition drive nor format the drive. Formatting or deleting the recovery partition drive can heavily affect the recovery of Windows since the data on the drive is used by the Windows Recovery Environment or your system’s manufacturer. A lot of users have reported that removing the drive letter has resolved the issue. And if you worry that removing the drive letter will delete the drive, you are mistaken. This solution is basically harmless and is proven effective to make the notifications go away. Carefully follow the instructions below to get rid of the Low Disk Space notification by removing the drive letter.

• Step 1: Tap the Windows key once.
• Step 2: Next. In the Windows Start Search, type in “command prompt” and right-click on Command Prompt from the search results and select the “Run as administrator” option or you could simply tap Win + R keys and then input “cmd” and hit Enter to open Command Prompt.
• Step 3: After opening Command Prompt, type in “diskpart” and tap Enter.
• Step 4: Next, type in “list volume” and tap Enter. After that, you will see a list of drives.
• Step 5: Take note of the letter associated with the newly created drive.
• Step 6: Afterwards, type in “select volume <drive letter>” and tap Enter. Take note that you must replace the <drive letter> with the drive letter you’ve found in Step 5.
• Step 7: Now type in “remove letter=<drive letter>” and then tap Enter. Once again, replace the <drive letter> with the letter you took note of in Step 5.

What is Error 1723?

Error Code 1723 is a peculiar error type common in Windows PC. It is related to the Windows Installer package. This error is displayed in the following format:

"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”

You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.

Solution

Error Causes

The 1723 error may occur due to several reasons, the most common being:

• Corrupted installers
• Files are not extracted successfully
• Registry problems
• Missing DLL files

Further Information and Manual Repair

To resolve this issue on your PC, you don’t always have to hire a professional technician and pay hundreds of dollars to get it fixed. The error code 1723 may not be a common Windows PC error but it is easy to fix. Here we have listed some of the best and easiest DIY ways to resolve this error on your system. These solutions are so easy to perform that even if you are not a computer programmer or technically adept, you can work through them and resolve the error in just a few simple clicks. So, let’s get started:

Solution 1: Install the latest Java Version

If the Java version previously installed on your system is not working properly and showing 1723 error messages then it is advisable to install the latest Java version. However, to do this first you will have to uninstall the old version and then download the latest Java version on your PC from a trusted website to ensure it does not contain malicious viruses and malware.

Solution 2: Ensure the Required Files are extracted in the ‘Temp’ Folder for Installers

Another method to resolve the 1723 error code is to check whether the required files are extracted in the temp folder for installers or not. The error may occur if the location is incorrect and the account is not permitted to extract files in the temp folder. In this scenario, the best way to resolve the issue is to change the permissions of the temp folder. This can be done by logging in to your account and opening file explorer or ‘My Computer’. Now copy and paste this link address in the address bar: DL:UsersUSERNAMEAppDataLocal. Please note, here DL is the drive letter of the Windows drive, and in the username insert the username of the account that you are using. Now right-click the ‘temp’ folder. Select properties and click on the Security tab. After that click edit below the list and press add. Again type the username here and click OK. The next step is to select the added account from the list and tick ‘FULL CONTROL’ box under ‘Permissions for Username’. Click OK and then close the properties. Once this process is complete, now try running the installer again. This will most likely resolve the issue. Nonetheless, if the error still persists, then this means the underlying cause of the error is deeper than you think. The error may be related to registry issues. In such situations, try solution 3 to fix the error 1723 on your system.

Solution 3: Download Restoro.

When the error code 1723 is triggered due to registry issues, then it is advisable to scan your PC with Restoro. Registry issues should be resolved immediately because they pose serious threats to your system. It can lead to system failure, crash and valuable data loss. Registry basically saves practically all the information and activities performed on your PC including the unnecessary and obsolete files like junk files, cookies, temporary files, and invalid entries. If these files are not removed they can corrupt the registry, damage dll files and installers thereby generating error codes like 1723 on your system. The easiest way to repair and clean the registry in seconds is to run Restoro on your PC. It is a smart, intuitive, advanced, and multi-functional PC repair tool. It is embedded with multiple powerful utilities and is a one-stop solution for all PC related issues. This software is compatible with all Windows versions. It is deployed with a highly functional registry cleaner that scans and detects all registry issues on your PC and removes them right away. It wipes out the unwanted files, repairs the damaged dll files and restores the registry. Other powerful utilities that are embedded in this software include an antivirus, a system optimizer and Active X controls and class modules. To resolve 1723 error code on your PC today, click here to download Restoro.

Microsoft office has set itself as one of the most used and best suites for business use and MS Word as the most widely used word processor. But how even best are not immune to some small bugs and unexpected behaviors so is not Word. Word has stopped working is probably know to a wide audience of its users, I think I could safely say that each Word user has experienced this error at least once, luckily the error is not anything to worry about since it is an easily fixable issue.

Try automated solutions

There are some fully automated solutions that could fix any PC issues, some are available in free versions. If you prefer to do things manually however keep on reading and follow the instructions below.

Manual FIXES:

1. Update MS Word

   Make sure that you are running the latest build of Word in order to eliminate all bugs and to have a smooth running experience. Go to File > Account > Product Information > Update Options and click Enable Update and then select Update Now.

2. Check the file

   Corrupted files can cause this crash and this error, try opening another text file inside the Word to eliminate file corruption.

3. Run Word in safe mode and disable add-ins

   Did you know that MS Word has a safe mode like Windows? In this safe mode, Word will boot up just the application without any add-ins installed and in this environment, you can start one add-in by one to see which one is causing the issue. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in winword /safe followed by ENTER to run Word in safe mode If MS Word works fine in Safe mode, disable all COM Add-ins (while being in safe mode) and restart Word. Re-enable the add-ins one at a time to identify the problematic one. Click on File and then on Options Click on Add-Ins from the options list Select COM Add-ins from the drop-down menu and click on Go Uncheck all the add-ins and click OK to confirm Close the Dialog Box and MS Word. Now try running MS Word normally and see if it works Repeat steps to enable the add-ins, one at a time, and check which add-in is causing this error

4. Repair Word installation

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type in control panel and press ENTER Inside Control Panel click on Programs and Features Locate and click on Microsoft Office to select it Once selected click on change located on top of the application list Once Office Windows loads click on Repair Wait for the process to finish

5. Reinstall MS office

   If all the previous solutions failed next step would be to completely uninstall MS Office and install it again once the old one has been completely removed from the system. Go to the control panel as explained in the previous step and select Office Instead of Change this time click on uninstall and follow on-screen instructions Once uninstall is finished, install a new copy of MS Office.

USB storage devices are used to store small and even big files, depending on their sizes. Usually, the sizes of the USB vary from 2GB up to 16GB. And as time passes, they have advanced quite a bit and now it’s common to find USB sticks with a capacity of 32GB, 64GB, or even 128GB. And since they now have large capacities, USB storage devices are often used for storing backups of system data as well as creating an image. However, there are times when you might encounter an error message while trying to create a backup or image on your USB device. The error message states:

“The drive is not a valid backup location.”

One of the causes of this problem is that Windows was not able to recognize the USB drives as a valid backup location since USB storage devices weren’t previously large enough to store system images. To fix this error, here are some possible solutions that might help.

Option 1 – Try creating a sub-folder in the USB drive and backup all the images there

The first thing you can try to do is to create a sub-folder on your USB device. This is one good way you can bypass the USB drive limitation. How? Refer to the steps below.

• First, right-click on the USB storage device and select Format.
• Next, select NTFS as the File System and check the box next to Quick Format.
• After that, click on Start to initiate the formatting process.
• Once the formatting process is completed, open the USB drive and right-click anywhere inside its main drive window, and then select New > Folder.
• Then name the folder to be created as “Image (or anything you please)”.
• Afterward, right-click on the folder and select Properties.
• From there, go to the Sharing tab and click on Share.
• Now check if the Permission level on the System owner which should be your username is labeled as “Owner”.
• Then try to back up your files again using your USB drive while keeping the sub-folder as the backup location.

Option 2 – Update the USB Controller Drivers

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Run CHKDSK utility to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. To use it, follow the steps below.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.

Valve has announced the first gaming PC handheld console: Steam Deck. At its core, Stead Deck is just a portable, small PC in little casing. It uses AMD Zen 2 CPU and RDNA 2 GPU architecture, has 16GB of RAM, Wi-Fi, and Bluetooth. It is a portable device with both a touchpad and joystick packing a seven-inch screen with a resolution of 1280x800 (16:10 aspect ratio). The screen has an ambient light sensor for automatic light adjustments same as your modern mobile device. Stating to Valve battery will hold up from two to eight hours depending on the activity of the user and what exactly he is doing. The handheld comes also with a carrying case.

Steam Deck operating system and software

Out of the box, Steam Dock comes with the latest Valve’s version of SteamOS 3. Just for comparing, the steam box was coming SteamOS 2, so this new Linux-based OS is aimed to provide better performance and better compatibility. Naturally, all Linux games in your Steam library will work right out of the box but Valve has something called PROTON inside OS, it is emulation software based on Wine that will supposedly let you play all of your Library games on a given OS. One big thing to mention here is that this is PC after all meaning that if you do not like having SteamOS on it you can install Windows instead and so far as we know it will support Windows 11. Now with Windows 11, you will be able to play all of your Steam games and run any kind of Windows software on it including EPIC store, battle.net, and others.

Cost and release date

The initial release date is set for December 2021 and today on July 16^th Valve is opening you can reserve your copy if you want to pre-purchase. Follow this link if you want to reserve your copy. Reserve your Steam Deck device The price of the device will depend on the memory capacity which you would like to have. Please note that each of the 3 offered devices will have the same hardware, the only difference will be in memory available, and the most expensive version will also have anti-glare screen, everything else is identical. 64GB model will be $399, 256GB model will have the price of $529 and largest one with whooping 512GB will be $649

Conclusion

Valve ventures into the digital hardware domain again but it is unsure will they make it this time. Both Steam machine and their controller were in long run failed and later unsupported products so perhaps some customer caution is advised. Although having a handheld PC is tempting I would advise seeing how the overall market will accept this contraption before throwing money into it.

It is common knowledge that when you open a file that contains viruses, it will automatically infect the operating system. This is why most antivirus programs like Windows Defender won’t allow the opening of a file or execution of any associated program if they detected that the file or program could potentially harm the computer. In situations like this, you may get an error stating, “Operation did not complete successfully because the file contains a virus”. In addition, it is also possible that this error message can pop up even for known programs. To open the program or file that triggered the error, you will be given a couple of options in this post but make sure that the program or file is really safe to open and does not contain any virus. You can open the file or execute the program by disabling the Windows Defender or any antivirus program temporarily. You could also try to add an exclusion in your antivirus program or repair File Explorer or run the Disk Cleanup tool. For more details, refer to each one of the options provided below.

Option 1 – Try to temporarily disable the Windows Defender program

Although you could encounter this error with any antivirus program, it is more common in Windows Defender. Thus, you can try to disable it for a while when you open the file or execute the program. To do so, follow these steps:

• First, click on the Start button and go to Settings > Update and Security > Windows Security.
• Here, select the “Open Windows Security” option located in the right pane.
• After that, click on the “Virus and threat protection” option.
• Next, click on Manage settings under the Virus and threat protection settings.
• Then turn off the switch for both Real-time protection and Cloud-delivered protection.
• Now restart your computer and try to open the file or execute the program again and see if it works.
• Note: Do not forget to enable the Real-time protection and Cloud-delivered protection back in Windows Defender.

Option 2 – Try adding an exclusion in the Windows Defender program

• Open the Windows Defender Security Center from the system tray area.
• Next, click the “Virus & threat protection” option and then open the “Virus and threat protection settings”.
• After that, scroll down until you find the “Exclusions” and click on the “Add or remove exclusions” option.
• Then click the plus button and select the type of exclusion you want to add and from the drop-down list, select Folder.
• Next, navigate to the path where the file or program is located.
• When a User Account Control or UAC prompt, just click on Yes to proceed.
• Now try to run the program or file again and see if it worked. If it did, then make sure to turn on your antivirus. However, if it didn’t work, proceed to the next given options below.

Option 3 – Try to run a System File Checker 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 with good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

 Now restart your computer and see if the problem is fixed or not.

Option 4 – Run the Disk Cleanup tool

You can also try using the Disk Cleanup tool. To use it, refer to these steps:

• Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
• After that, select the drive you want to clean.
• Now click OK to clean the disk and restart your computer.