Enable or Disable Auto-Mounting in Windows

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.

One of the biggest annoyances in Windows 10 is that it’s upgrading from one version to another. Although these upgrades are necessary to fix some bugs or improve user experience, some of them actually bring bugs into the computers instead. And in one of the recent Windows 10 updates, a lot of issues were found especially for users who use Remote Desktop on a daily basis. The error stacks up as Windows 10 Remote Desktop Protocol client is not working or won’t connect and can’t find the computer HOSTNAME generally. Based on the reports by users who experienced this issue, there are two cases around it:

1. Users who try to reach a specific website or folder on the network

Some users encounter this error when they try to run the Network Troubleshooter. Even when they add the server name inside it, it still won’t identify the problem, and unpredictably, the driver seems to appear and disappear every now and then. And even after connecting, the network commands don’t work at all. This is really troublesome for users who have lots of PCs and all the other systems do not appear on the network.

2. Remote Desktop isn’t able to find the computer HOSTNAME

Some other users reported that the error appeared when they use the classic remote desktop software. It keeps on failing and throwing the error message, “Remote Desktop can’t find the computer “HOSTNAME”. If this is the same scenario you are having, it means that “HOSTNAME” does not belong to the specified network. So you need to verify the computer name and domain where you are trying to connect to. There are times when it used to work after some users tried connecting to the domain a couple of times. However, when users try to use the UWP version of Remote Desktop, it seems to connect most of the time. This kind of problem is definitely a DNS issue. It could be that there are two different records on the DNS server which is why it connects and other times it doesn’t. When it is able to resolve the correct address, the drives connect to the PC however, after a couple of minutes, they will suddenly go missing. Using “nslookup” for the hostname, multiple times, you can check this and see if you’ll get identical results all the time.

nslookup [–SubCommand …] [{ComputerToFind| [–Server]}]

If you’ve determined that the drives disappear each time, you may have to change the DNS server or ask your admin to resolve the problem for you. Alternatively, you can also check out another option that has worked for a lot of users. This second option is disabling the IPv6 on the network adapter. In case you don’t know, Windows 10 prefers IPv6 over IPv4 so if you now have issues using IPv6 to connect to the servers, you can change your computer’s settings so that it’ll only use IPv4 instead of IPv6. To do so, follow these instructions:

• Open Settings > Network and Internet > Ethernet > Change Adapter options.
• From there, right-click on the adapter for where you want to disable it and then select Properties.
• Next, look for the checkbox labeled, “Internet Protocol Version 6 (TCP/IPv6)” then uncheck it.
• Now click on OK and restart your PC to save the changes made.

A surprisingly large amount of things present at your home can and do interfere with your wi-fi signal making it weak so devices are dropping it, having trouble connecting, or being slow.

Hello and welcome to our latest article where we will take a look at all things that are present in a lot of homes but are very bad for your WI-Fi signal.

Bad router placement

Having a router in a bad position can have some really large effects on WI-Fi signal strength and its availability. Usually, we do not give great attention to where we are placing our router but it has been proved over and over again that being close to certain objects does indeed have a great influence on the wireless signal strength and performance.

So, what are these objects and bad positions where we could place the router and effectively kill his Wi-Fi capabilities?

Fish Tanks

Water will block all radio waves including Wi-FI signals and waves themselves, so having a router next to the aquarium or any large source of water is a bad idea. You should always look at water as something bad for your Wi-Fi and move your router away from it as far as possible.

Bookshelves

Paper is another story and example of the dampening effect on radio waves. Did you know that various patterns of paper are used in silent rooms and recording studios in order to eliminate sound reflection from surfaces? Well besides absorbing sound waves, the paper also absorbs Wi-Fi signals and if you have a large bookshelf with a lot of books packed one beside another you just have a great wall of signal absorbing.

Mirrors

The problem with mirrors is in their coating that goes over the glass in order to turn it into the mirror, that coating is metal and as such, it is absorbing signals in large amounts. If you have an old or high-quality mirror that has a silver coating things are even worse since silver will absorb even more waves than modern cheap ones.

TV

Yup, TV is also on this list and for a similar reason as a mirror, although TV does not have coatings of metal, they have something even worse: a large metal plating on the back. Metal plating is there to produce structural integrity of the TV set and provide it with shielding from electromagnetic waves and as such it will prevent Wi-Fi waves as well. Do not place the router behind your TV.

Things that influence signals in homes

Any kind of metal decoration

Now when we covered mirrors and TV because of the metal they have, we must take a look at the metal itself. Any kind of metal stuff that you might have like baskets, figures, statues, frames, etc will effectively block your signal.

Kitchen appliances and Home utilities

Kitchen appliances like refrigerators, microwaves, ovens, stoves, etc. along with home appliances and utilities like dishwashers, washing machines, dryers, etc are large metal objects enclosed in a metal cage that will block signals from spreading further and it is no secret that most kitchens have weaker Wi-Fi because of this reason.

Home gyms

This is a logical conclusion as to everything explained so far if you have a workout room or small gym at home it is probably filled with weights that are metal and have mirrors inside, all of that will interfere and block signals.

Things blocking your Wi-Fi that you have no easy control over

Walls

Thick walls will dampen signals, thick walls from bricks will dampen even more and concrete walls will kill it almost completely. Any kind of metal reinforcement wiring inside walls will reduce and kill signals as well.

Floors and ceiling

This is somewhat important if you have a floor beneath or under the room where is your router located, but for the same reason how walls are blocking your signal floor and ceiling can do it as well, especially since most of the time they are made of some stronger material like concrete with metal fence inside.

Heating systems

If you have a heating system that is composed of metal radiators with water inside, then in terms of Wi-Fi signal strength you have an aquarium but in a metal box, and as such it will greatly reduce signal strength.

A command is not recognized Error, what it is? If you are constantly using programs like CMD or DISM directly from the Run prompt, you might have wondered how they launched instantly and how is it that the Windows operating system is able to find them right away. For instance, when you create a shortcut of a program, the shortcut knows where exactly the program is located and launches it quickly. The Windows operating system keeps a list of paths where the most common system programs are located so when you use the Run prompt, it opens easily. The list kept by Windows is called the Windows Environment Variables. If something goes wrong with this list, the programs won’t work. So in this guide, you will be guided on how you can troubleshoot the problem where any command you use is not recognized as an internal or external command, operable program, or batch file. Before you start troubleshooting the problem, you need to make sure that the program you are trying to run really exists. In fact, this can also happen to the Run program which is pulled up using the Win + R shortcut. To check, go to C:\Windows\System32 and there, check if the program exists or not or you can also try searching for the EXE in the System 32 folder. After making sure that the program exists, refer to the instructions given below.

Modify the Windows Environment Variables:

• Step 1: Tap the Win + X keys and then select System. After that, it will open the section where you can see all the properties on your computer.
• Step 2: Next, select the Advanced system setting located on the left pane and click on the Environment Variables.
• Step 3: After that, locate Path under the System Variables and select EDIT.
• Step 4: Before you edit, you need to copy the entire string and paste it into the Notepad app so that in case something went wrong, you can paste it back.
• Step 5: Next, look for the directory path, “C:\Windows\System32”. If you can’t find it, try adding a semi-colon at the end.
• Step 6: Afterwards, click OK to save the changes made and then exit.
• Step 7: Now restart your computer as all the paths are picked up when your computer restarts.

Note: Now all you have to do is to try executing the programs once again – the ones where you got the error, “ is not recognized as an internal or external command, operable program or batch file” every time you open them and then see if you can now open these programs or not.

This post will guide you in fixing the “Communication with service process failed” error in Windows 10. This error is related to the Intel Driver and Support Assistant application. Although this error does not reportedly cause any loss of functionality in the computer, however, it still indicates that there is something wrong with some of your driver modules. Intel has taken a bold step and combined its older modules into this new application (Intel Driver and Support Assistant) recently. This application enables users to scan their computers for any available updates from Intel. This is the main application of Intel and provides users a way to update their driver software automatically instead of manually updating it. However, with the recent reports submitted by some users, it seems that something is wrong with this application, and users to have to deal with the “Communication with service process failed” error. This error might be caused by several reasons, for one, it could be that the application is corrupted or incomplete in its nature which is possible since this is still a developing and newly released app. It could also be that there are other utilities or modules that conflict with the Intel software. Whichever the reason may be, you can try out the options given below to resolve the problem but before you proceed, make sure that you have an administrator account as well as an active and stable internet connection.

Option 1 – Disable DSATray in Startup

If you receive this error message every time you start your computer then this means that the application is not able to launch properly. Like pointed out, it could be that it is still incomplete in nature or it conflicts with other applications. Thus, you can try to disable the service from the startup and check if it fixes the problem.

• Tap the Win + R keys to open the Run dialog box.
• Then type “taskmgr” in the field and hit Enter to open the Task Manager.
• After that, go to the Startup tab and look for the Intel Driver and Support Assistant app.
• Right-click on the app and select Disable.
• Restart your PC and check if the error is now fixed or not

Option 2 – Reinstall the Intel Driver and Support Assistant

If the first option did not work, you can try reinstalling the Intel Driver and Support Assistant app. To do so, follow these steps:

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for Intel Driver and Support Assistant and select it and then uninstall it.
• After you have the app uninstalled, open your browser and go to Intel’s official website. From there, download the driver utility manually.
• Once the download is finished, right-click on it and select “Run as administrator” and install the app on your PC with elevated access.
• Restart your PC and then check if the error is now fixed.

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

Reasons to upgrade to the new OS

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

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

Reasons to avoid Windows 11 for now

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

Conclusion

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

If you are in the process of booting up your computer but suddenly encountered an error saying, “The Boot Configuration Data for your PC is missing or contains errors” with an error code of 0xc0000454, read on as this post will help you resolve the problem. The error code 0xc0000454 occurs when you boot your computer and when the Windows Boot Manager encounters an issue with the Boot Configuration Data or BCD. The error code 0xc0000454 (STATUS_INSUFFICIENT_NVRAM_RESOURCES) signifies that there are no sufficient NVRAM or Non-Volatile Random Access Memory resources to complete the API. NVRAM is a component of the system based on the software that stores the Boot Configuration Data in an operating system. Usually, a simple restart can resolve the problem. However, if you’ve already done that and it’s of no use, then there are other potential fixes you can check out to troubleshoot the problem. To resolve the error code 0xc0000454, here are some potential fixes that should help:

Option 1 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:

• You need to go to the Advanced Startup Options.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
  • Bootrec /Fixmbr
  • Bootrec /FixBoot

• After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
• Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
• Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – 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.

Option 3 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 4 – Try to reset the BIOS

If updating the BIOS didn’t help in fixing the error, you can try to reset the BIOS instead.

• Start your computer and tap the F10 key during the booting process to enter the BIOS. If it does not work, you can try tapping the F1 or F2 key as well as the Del key.
• Once you’re already in the BIOS, tap the F9 key to get the prompt to RestoreLoad default configuration now for the BIOS.
• Next, click on Yes and then follow the next on-screen instructions that appear to set the BIOS back to its default settings.
• Once you’re done restoring the default settings of the BIOS, restart your computer and then check if it now boots properly.

There are cases when your Windows 10 PC can encounter an issue where it gets stuck and will display a message that says, “Preparing Security Options”. If this is happening to your Windows 10 PC, you won’t be able to use your keyboard or even mouse and your screen will only be stuck on the screen as mentioned above. As your computer is still stuck, you will be left with no choice but to shut it down and restart it. Tap the F11 key as soon as your PC powers on. This will take you to the Advanced Startup options where you can carry out some steps. If it still didn’t work, you have to boot your Windows 10 PC into Safe Mode and then try out the troubleshooting options below.

Option 1 – Try using System Restore

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.

Option 2 – Uninstall the Windows Updates you’ve installed recently

The issue could be caused by Windows Updates so you need to check if it’s indeed the case. The best way you can do so is via Safe Mode.

• Boot your PC into Safe Mode and then tap the Win + I keys to open Settings.
• After that, click on Update and Security and then select Windows Update from the left side menu column.
• Next, select the “View installed update history” option on the right-side column and click on Uninstall Updates which will open a window that will show the list of all the installed updates on your PC.
• From there, select the update you want to uninstall and click the Uninstall button located in the lower right corner of the window.

Option 3 – Try disabling the Fast Startup

• Boot your PC into Safe Mode.
• Then tap the Win + R keys to open the Run dialog box.
• Next, type in “control” to open Control Panel.
• After that, select Hardware and Sound and click on Power Options.
• Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
• Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
• Now restart your PC and check if the problem’s fixed.

Option 4 – Try running both the SFC scan and CHKDSK utility

You can do both SFC and CHKDSK using Safe Mode and Advanced Startup options. For Advanced Startup options, click on the Command Prompt option and proceed with the steps. And if you have booted your computer into Safe Mode, follow these steps:

• Tap the Win + X keys or right-click on the Start button and click Command Prompt (admin).
• After that, type in this command and tap Enter to run the System File Checker or SFC – “Sfc /scannow”.
• Alternatively, you can use this command instead if the previous command didn’t work – “sfc /scannow /offbootdir=c: /offwindir=c:windows”.
• Wait until the SFC scan is done with the process and then restart your PC.
• Next, run the CHKDSK utility and once it’s done checking your disk for errors and then reboot your PC to save the changes made.

Option 5 – Try resetting Windows 10

You can reset your Windows 10 PC using either the Advanced Startup Options or by booting into Safe Mode.

• Tap the Win + I keys and go to Update and Security > Recovery.
• Then click on Get Started under the Reset this PC section.
• After that, follow the on-screen instructions with how you want to reset your PC and what files and settings you want to revert.
• Then it will reset your PC by reinstalling it

Option 6 – Try to rename the SoftwareDistribution folder

In this option, the Command Prompt is supposed to be like the one in option 4. You can use both ways there to open the Command Prompt.

• Open an elevated Command Prompt as admin and type in the commands below and tap Enter right after you typed in each one of them
• net stop wuauserv
• net stop bits
• rename c:windowsSoftwareDistribution SoftwareDistribution.bak
• net start wuauserv
• net start bits

Note: You can also rename the SoftwareDistribution folder to “SoftwareDistribution.bak” or “SoftwareDistribution.old” after you boot your PC into Safe Mode.

Option 7 – Try rebuilding BCD

Rebuilding the BCD can help you in fixing the stuck Windows 10.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
• exe /FixMbr
• exe /FixBoot
  • exe /RebuildBcd

If you are trying to access a particular file on your Windows 10 computer either to open, rename or delete it, and you suddenly encounter an error stating, “Could not find this item. This is no longer located in [Path]. Verify the item’s location and try again”, read on for this post will help you out in resolving this issue. If you are able to find and view a file on your computer, you should have clear access to it. And since you are seeing an error message when you try to do something about this file, you are not able to do anything with the file. There are times when this error pops up with the files created by third-party services and that the file’s extension is not defined properly. On the other hand, there are also other obscure causes for this error. To fix it, here are some suggestions you can try.

Option 1 – Delete the file using Command Prompt

If you wish to delete the problematic file and weren’t to, you can use Command Prompt.

• In the Start menu, type in “Command Prompt” to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator”.
• Once you’ve opened Command Prompt, copy and paste the command given below and tap Entre after you do so. You also have to make sure that you key in the correct path where the file is located as well as its name.

rd /s \?X:badfolderpath Note: In the command above, “X” is the placeholder letter so you must input the letter that corresponds to the drive’s letter where the file is located.

• After that, you will see the “Operation completed successfully” message on your screen. If you don’t, check if you’ve really inputted the correct location of the file or its name.

Option 2 – Use a Command Prompt tweak to rename the file

If you don’t want to delete the file and only want to rename it, you can apply some tweaks using the Command Prompt. Make sure to follow the steps carefully.

• In the Start menu, type in “Command Prompt” to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator”.
• After opening Command Prompt, type in “cd” followed by the path where the file is located with this format – “C:\Folder1\Folder2\Folder3”. However, you have to omit the problematic file this time. To put it simply, the last folder in the command must be the folder where the file is located.
• After inputting the command, tap Enter on your keyboard and then use the set of commands given below. Note that each command is a new line so you need to tap Enter after copying each line.
  • DIR /A /X /P
  • RENAME (the current name of the problematic file) (a non-problematic name)
  • EXIT

Note: Make sure that you only input the current name and the new name separated by a space. You must not write the brackets in the command. If everything goes well, you will now be able to operate the file like you used to before.

Option 3 – Use Command Prompt to delete the file without any extension

This option applies to cases where the affected file does not have any viable extension which means that Windows does not really know what to do with it and it only displays the “Could not find this item. This is no longer located in [Path]. Verify the item’s location and try again” error message. It usually occurs with the files created by browser plugins that are mostly from Mozilla Firefox. To delete these kinds of files, here’s what you have to do:

• Follow the first two steps from the previous option above so you can navigate to the location of the file accurately just be careful in inputting the folders.
• Don’t forget to tap Enter right after each command and then use the next command below so you can delete the affected file which has no extension:

del *.*

• After you’re done, open the File Explorer and then check if the file is now deleted or not.

Option 4 – Try using another workaround without using Command Prompt

This option is a lot like a workaround but it definitely gets the job done for you. It’s ideal for you if you do not want to deal with Command Prompt and only want to do everything in a graphical environment. To get started, follow the steps below.

• Look for the affected file or folder on your PC using File Explorer. Once you found it, right-click on it and select the “Add to archive” option from the context menu.
• Once the archiving options window pops up, look for the “Delete files after archiving” option and make sure that you select it then click OK to start archiving the folder or file. After that, you should now notice the file no longer exists.
• After that, delete the archive file as well.

If you got encounter an error message saying, “Error opening file for writing” while running a setup file to install some program on your computer, read on as this post will give you some suggestions on how you can fix it. You can encounter this error when running a setup file for installing a program like GlassWire, Notepad++, VLC, Steam, OBS, Mod Organizer, WinpCap, NSIS, FileZilla, BSPlayer, Kodi, Wireshark, rtcore64, qt5core.dll, MSI Afterburner, GWCtlSrv.exe, npf.sys, vcredist_86 and many more. And so when this error pops up while you run a setup file, refer to the steps given below which might help resolve the problem. Step 1: First, you have to make sure that there is no other installation in progress as multiple installations can most likely cause this error to show up. You can restart your computer and try to run the setup file again. Step 2: If you still got the error even after your restart your computer, click on Retry to try again and if it does nothing, click Abort to terminate the installation. After that, go to the folder where you’ve placed the setup file and then delete it. Step 3: Make sure that you have enough disk space on your computer. You can use the Windows 10 Storage Sense feature which can clean all the temporary files from your computer and help you save storage space. To use Storage Sense, follow the steps below.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• The system created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again. Step 4: If freeing up space didn’t help, you can just delete the setup file and download another one from the official homepage of the program. From there download the setup file and place it in a different location. After that, run the setup file once again. Step 5: Make sure that you have downloaded the correct setup file according to your operating system, i.e. x64 or x86. Step 6: Restart your computer once more and make sure that you sign in as administrator. After that, right-click on the setup file and click “Run as administrator”. If it still didn’t help, you might want to take ownership of the folder where you saved the setup file. How? Follow the steps below but before you do that, you have to create a System Restore Point first, once that’s done, proceed.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.