Windows 10 tips and tricks for easy work

Lately, some users reported getting an error that says, “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” when they tried to reinstall the Windows 10 operating system on their PCs or boot from an installation media. If you have the same problem, then this post should help. This kind of error is applicable to multiple devices by various OEMs and is mostly due to the Secure boot being enabled, or the Legacy or CSM support being disabled. It could also be that the bootable USB device was not correctly made and so on. Whatever the cause may be, here are some suggestions you need to check out to resolve the “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” error and reinstall Windows 10 successfully.

Option 1 – 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 2 – Try to reset the BIOS or the UEFI Settings

If updating the BIOS didn’t help in fixing Error 0199, 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.

Option 3 – Make a proper bootable USB Drive/Stick

To make a proper bootable USB drive, you need to use the Windows Media Creation tool. The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

Option 4 – Try enabling Legacy or CSM boot support

If the Legacy or CSM boot support is disabled, then it’s no wonder why you’re getting an error. Thus, you need to enable it by following these steps:

• Open Settings and go to Update & Security > Advanced Startup options.
• Next, click on Restart Now to reboot your computer.
• After that, select Troubleshoot > Advanced Options where, you will see more options such as System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• From there, enable Legacy Support and then save the changes and exit. This will restart the computer.
• Once your computer has restarted, check if the error is now fixed.

What is Error Code 29?

Code 29 is a Device Manager error commonly seen whenever a hardware device driver reports a problem. This error code indicates that the resources needed for operation are not available.

The computer hardware basically requires drivers to interface with the operating system. Drivers comprise multiple components and are supplemented with other resources provided by the BIOS (a physical chip on the motherboard).

The BIOS contains a set of basic input and output instructions for the computer system to boot, load drivers, and more.

Its firmware provides resources that drivers require to interface with other essential components. However, when the firmware fails to provide the requested resources, the device drivers stop functioning; this results in error codes like code 29.

Error code 29 is usually displayed in the following format:

“This device is disabled because the firmware of the device did not give it the required resources” Code 29

Solution

Error Causes

Error code 29 may be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• BIOS misconfiguration
• The device firmware is corrupt
• Previous attempt to update the driver failed

To avoid inconvenience and to ensure your computer keeps working at its optimal pace, it is recommended that you repair error code 29 on your PC immediately. Delay may limit you from using certain hardware attached to your system properly.

Further Information and Manual Repair

To repair error code 29, you don’t have to hire a professional and spend hundreds of dollars. Here are some quick and effective DIY methods that you can try to resolve this issue in minutes even if you don’t have any technical background.

Method 1 - Reboot Your PC

Sometimes, error codes like code 29 may pop up on your computer screen due to some temporary glitch with the hardware. Rebooting can resolve the issue easily.

Therefore, before you do anything, try restarting your PC. It could be all you need to repair code 29. However, if the error code continues to persist, try the other methods given below.

Method 2 - Clear the CMOS

This may sound technical but it isn’t. To begin, with CMOS is an acronym for Complimentary Metal Oxide Semiconductor.

It is a term that is used to describe motherboard memory that contains the BIOS settings. Clearing CMOS helps reset the BIOS settings to their default manufacturer levels. It’s easy to do and is an effective troubleshooting step to resolve error code 29.

To do this, simply:

1. Enter the BIOS setup utility  by restarting your PC
2. Watch for an entering setup message
3. Enter the BIOS access key. Usually, the key is F2 or F12. However, the key may differ from manufacturer to manufacturer. You may want to check the manufacturer’s website first to find out the BIOS access key before you restart your PC.
4. ‘Reset BIOS settings’ to their default factory levels.

Method 3 - Enable the Device in the BIOS

Error code 29 may appear if a device is disabled. In such a scenario, simply follow the same steps as discussed in method 2, and in the advanced BIOS settings, look for disabled devices.

Enable the devices in the BIOS so that you use them easily.

This will hopefully resolve the issue. If it doesn’t, then this means the error code 29 is caused by either corrupted or outdated drivers. Try method 4 to resolve this issue successfully.

Method 4 - Identify the Problematic Device Drivers and Update them

Whether the error code 29 is caused by a misconfigured, corrupted, or outdated driver, simply update the new driver version to resolve. When doing it manually, you will first have to find and identify the problematic device drivers in the Device Manager.

You can access the Device Manager by going to the start menu and then simply typing Device Manager in the search bar.

Access the Device Manager and the properties to identify problematic drivers. Problematic drivers are normally displayed with a yellow exclamation mark.

Once you have spotted problematic drivers, simply update new drivers to resolve them. Though there is nothing technical about it but it may be time-consuming.

Method 5 - Install Driver Assist to Update Drivers Automatically and Regularly

A good alternative to manual driver update is DriverFIX. Simply download and install DriverFIX on your PC to update all problematic drivers in seconds. This is a cutting-edge program designed to resolve all kinds of device driver problems.

It is user-friendly and compatible with all Windows versions.

The intelligent programming system deployed inside this software program enables it to identify and detect all problem drivers automatically thereby sparing you from the hassle.

Furthermore, it also matches the drivers with the latest and compatible versions and updates them on a regular basis.

It takes the guesswork out of finding misconfigured and corrupted drivers and fixes driver-related problems and error codes like code 29 right away.

Click here to download DriverFIX to repair Device Manager error code 29 on your system without any hassle.

What is Mapi32.dll Outlook Error?

Mapi32.dll is a Windows Messaging Application Programming Interface that enables Windows to perform various email functions and launch messaging programs like Microsoft Outlook and Microsoft Office. The inability of the interface to execute email functions properly results in the Mapi32.dll Outlook Error. This error occurs mostly when you are attempting to upgrade the operating system to a new version.

Solution

Error Causes

The common causes of the Mapi32.dll Outlook Error during the OS upgrade are:

• Damaged or Corrupt Outlook user profile
• The software is overwritten by some other program
• Outlook PST file corruption

The Mapi32.dll Outlook Error message is displayed in either of the following forms:

• Mapi32.dll is missing
• Cannot start Microsoft Office Outlook. Mapi32.dll is corrupt or the wrong version.
• Mapi32.dll was not found
• Mail is not installed

Further Information and Manual Repair

So, what if you experience this issue and how do you fix it? Well, first there is no need to panic as Microsoft has recognized this issue and provided adequate solutions to fix this problem in no time. However, to ensure the Mapi32.dll Outlook error is a quick fix, you must first understand the cause of the issue and the message displayed on the screen.

1. Let’s say the errors occur because your Outlook profile is corrupt. In this scenario, the best solution is to create a new Outlook profile. Regardless of whether you have Windows Vista or XP, to create your new Outlook profile, first, you will have to click on the Control Panel, then User Account, and then Mail. Once you click on the Mail tab, the mail set up dialog box will open. In this dialog box there will be a ‘Show Profiles’ tab, click and then click the Add tab that appears next. Now type the name for your new Outlook profile and then click ‘OK’. After that, add an email account to go with the profile.
2. If Mapi32.dll is missing or corrupt, you will have to run ‘Fixmapi.exe’ to resolve the problem. It is located in the System32 folder inside the Windows directory in Windows Explorer.

• Therefore, first start Windows Explorer and then locate the following folder on your computer: C: /Program Files/Common Files/System/Msmapi1033
• Now find Fixmapi.exe and double click it
• After that locate the Mapi32.dll file and rename it to MSmapi32.old and press enter.
• Restart your computer when finished.

A word of advice for computer users is to scan for viruses with an antivirus program or a registry cleaner regularly to prevent the Mapi32.dll Outlook error from occurring in the first place. Viruses often latch onto .dll files and corrupt them. It’s always best to have a forward-looking approach.

If you encounter the ERR_SSL_VERSION_INTERFERENCE error on your Google Chrome browser then this means that the browser is trying to load a website with SSL protocol but is not able to do so. This error can occur for many reasons and in this post, you will be given potential fixes that could help you in resolving the problem. But bear in mind that these potential fixes are not that straightforward forward so if you encounter an option you don’t understand much, just skip to the options you have the knowledge of. There is no direct fault in the browser for the ERR_SSL_VERSION_INTERFERENCE error as there are issues with caching the website data locally on your computer. Moreover, this kind of error can also appear when a website is coded incorrectly or if there are conflicting browser extensions installed in the browser that prevents the website to function properly. Refer to the suggestions given below to fix the ERR_SSL_VERSION_INTERFERENCE error in Chrome on Windows 10.

Option 1 – Try clearing browser data

There are times when some data in the browser is conflicting with the loading of the website and triggers errors like ERR_CACHE_MISS. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

• Open your Google Chrome browser.
• After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
• Now select every checkbox that you see and click on the Clear browsing data button.
• Then restart your Chrome browser and check if you can now open any website or not.

Option 2 – Try disabling TSL 1.3

If clearing the browser data didn’t fix the problem, you can also try to disable TSL 1.3 in Chrome. To do so, refer to these steps:

• Open Google Chrome.
• Next, type in “chrome://flags/#tls13-variant” in the address bar and tap Enter.
• After that, you should see the experimental features page for Google Chrome where you can set TSL 1.3 to disabled.
• After disabling TSL 1.3, restart your computer and check if the problem is fixed or not.

Option 3 – Reset Winsock, TCP/IP & Flush DNS cache

Resetting Winsock, TCP/IP, and flushing DNS might help in resolving the ERR_SSL_VERSION_INTERFERENCE error just follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 4 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Option 5 – Reset Google Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome will restore its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

If your Microsoft Edge browser and Windows Store apps are now unable to connect to the internet after you have just installed the newly released Windows 10 v1809 October 2018 update, then this post might help. As you know, Microsoft has made a change recently and because of this, some users are getting the “Hmm, we can’t reach this page” error when they try to open Microsoft Edge as well as other pre-installed apps like News, Mail, and so on. Aside from that, you also won’t be able to connect the Microsoft Store apps to the internet. What’s strange is that you can connect to the internet using other programs like Google Chrome, Internet Explorer, and many more. Apart from checking your internet connection, there are other things you can to resolve the problem. If your Windows Store apps are not able to connect to the internet and you’re only getting the Error 80072EFD, then you might have to enable IPv6 as the new Windows 10 v1809 requires IPv6 to be enabled so that you can use the UWP apps. And so you have to enable IPv6 in the network card along with IPv4. To do so, follow the steps below. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that, type “ncpa.cpl” and hit Enter or click OK to open Network Connections. From there, you will see your currently connected network profile. Step 3: Right-click on your network profile and select Properties and then go to the Networking tab and look for the “Internet Protocol Version 6 (TCP/IPv6)” and select its corresponding checkbox. Step 4: Now click the OK button to save the changes made and restart your computer.

If you encounter an error message that states, “Your computer has lost the lease to its IP Address <IP ADDRESS> on the Network Card with network address <NETWORK ADDRESS>”, then this post might be of help to you. This kind of error due to the timeout caused by the DHCPv6 address which is used to connect the client to the user network as an independent client or a part of a domain. There are a lot of potential fixes you can try to fix this error and we will be discussing each one of them below. You can try to reboot your router, flush the DNS cache, reset the Network adapter, toggle the DHCPv6 Lease time or disable IPv6 in the Network Center. For more details, refer to the following options.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

One the other hand, you could also try to reset Winsock as well as the TCP/IP. Once done, just exit the Command Prompt and check if that fixes your issue. You may want to reset Winsock & reset TCP/IP as well.

Option 3 – Try to toggle the DHCPv6 Lease time

• First, you need to log in to the Admin panel of your router.
• Next, navigate to the DHCPv6 settings inside it and look for a field for Lease Time.
• After you’ve found it, increase the Lease Time value to something greater than what is already entered depending on your preference.
• Now apply the configuration and reboot your router to apply the modified settings. Just remember that if things didn’t work out, you can just change back the Lease Time value to what it was before.

Option 4 – Try disabling the IPv6 in the Network Center

• Tap the Win + X key combination and click on Network Connections.
• This will open the Settings app on a specific page. Now on the right-side panel, click on the Network and Sharing Center link.
• After that, it will open the Control Panel and from there, click on the network that your computer is connected to and then click on Properties.
• Next, uncheck the entry that says, “Internet Protocol Version 6 (TCP/IPv6)” in the list that populates.
• Now click on OK and close all other windows and see if the error is fixed.

Option 5 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 6 – Try to perform Network Reset

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

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.

What is Error 0xe0434f4d?

Error 0xe0434f4d displays when a remote computer runs an instance of the SQL Server 2005 but it fails to initialize. When the plan is started, this error displays in a status window on the SQL Server. Also, when the Update-OffilineAddressBook cmdlet is started in Microsoft Exchange Server, this error can occur.

Solution

Error Causes

Error 0xe0434f4d can occur for possibly two main reasons. The first one is when the System Attendant Service is not properly running, and the second when you don’t have the permission to run the update. Other causes are when the .NET Framework 2.0 security does not allow sqlplanlaunch access to run from a shared network. Another cause is when the Offline Address Book (OAB) is not found in the Configuration Domain Controller server that the server of OAB generation uses.

Further Information and Manual Repair

In case you didn’t know, the Offline Address Book generation server is a mailbox server, and in order to resolve error 0xe0434f4d, you will have to replicate the OAB object to the Configuration Domain Controller server. In order to do so, follow steps:

• Go to start and click on All Programs, then go and click on Microsoft Exchange Server 2010. Click on Exchange Management Console
• In Exchange Management Console, go to Server Configuration and click on Mailbox
• In the details, go to mailbox server that generates Offline Address Book and right-click it, then go to Properties
• In the Properties, click on System Setting and locate the domain controller name in the box that reads Domain controller servers being used by Exchange

Make sure the OAB object is reproduced in the Configuration Domain Controller Server. Follow these steps to do that:

• Go to Start and click on Run. Type Adsiedit.msc in Open box and press Enter. Right-click on ADSI Edit and click on Connect to
• Locate a list reading Select a well-known naming context, and from there select Default naming context. In a Select or type a domain or server window, type FQDN (fully qualified domain name) of the Configuration Domain Controller server which was determined in step 1, and click OK
• Expand Configuration [dc.domain.com], expand CN=Configuration, DC=domain, DC=com, expand CN=Services, expand CN=First Organization, and expand CN=Address Lists Container
• Click on CN=Offline Address Lists and make sure the OAB object is listed on the details pane

When the OAB generation server receives this, then it will connect to the Configuration Domain Controller server and will locate the OAB object. If the OAB generation server is unable to find the OAB object, then the error will return on the cmdlet. On SQL Server, you should change the .NET permissions to allow sqlplanlaunch application access to run from shared administration. For that, follow these steps:

• On ArchiveIQ Server, open System from the Control Panel and note down the computer name
• On SQL Server, log in as administrator and open the command prompt
• On the command prompt type, ‘C:windowsmicrosoft.netframeworkv2.0.50727caspol.ece –m –ag l – url file:\[Archive IQServer Computer Name]AlQRemote$*FullTrust and Press Enter. Type yes and press Enter again to confirm the permission changes.

System image backup error 0x807800A1 & 0x800423F3 appears when you are trying to create a system image backup and the operation fails to do so. If you’re faced with any of these error codes, try our recommended solutions in the order presented below and resolve the issue.

Check Volume Shadow Copy & Software Protection Services

To restart the Volume Shadow Copy Service (VSS) on Windows 10, do the following:

• Press ⊞ Windows + X to bring up the Windows menu.
• Click on command prompt (admin)
• In the command prompt window, type the commands below and hit Enter after each line:

net stop vss net start vss

Once the commands execute successfully, try the system image backup again. The operation should complete successfully. You need to also check if the Software Protection Service is disabled. If it is, then Start it and ensure that it is set to default which is Automatic (Delayed Started).

Create System Image using PowerShell

Command lines are less prone to errors provided the syntax is correct, unlike GUIs that can suffer a glitch every now and then. To create a system image with PowerShell do the following:

1. Open the Windows PowerShell as administrator. To create a System Image in Windows 10 using PowerShell, you will have to run the Wbadmin command.
2. Inside the Powershell window type, then press Enter: wbadmin start backup-backup target: E:-include: C:-quiet-allCritical E: is the target drive where you’re going to save the system image, and C: is the system root drive where Windows is currently installed
3. To extract the created system image, starting over from Windows 10 USB installation media, select advanced startup or open run and type: C: \ Windows \ System32 \ Shutdown.exe / r / o

Use third-party imaging software

If the previous two solutions have not managed to solve the issue there is always an option to use a third-party imaging solution. There are free open source and buying options offering various advantages each. Find out which one works best for you and use it.

For PC users that are blind or have low vision, the Narrator accessibility feature in Windows 10, lets you use your PC without a display or mouse to complete common tasks – it reads and interacts with things on the screen, like text and buttons. The narrator can be used to read and write an email, browse the internet, and work with documents. In Windows 10, there are a lot of options for Narrator that you can customize. You can change its keyboard shortcuts, personalize Narrator’s voice, enable Caps Lock warnings, and more. You can choose the voice for the Narrator, adjust the speaking rate, pitch, and volume. To change the default audio output device used to play the voice of the Narrator in Windows 10:

• Press the ⊞ WINDOWS + I
• From the Settings menu, click Ease of Access.
• Click Narrator on the left pane.
• In the Narrator window, on the right pane, toggle the button to On to enable Narrator if required.
• Scroll down to the Personalize Narrator’s voice section.
• For the Select where you hear Narrator’s voice option, click the drop-down and select the audio output device you want from the list. Please know that you will not be able to choose if you do not have multiple audio output devices connected to your Windows 10 computer.
• Exit Settings when done.

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.