A Guide to Fixing Error 101

In any Windows operating system, Safe Mode is definitely a special environment used for troubleshooting issues as well as system diagnostics. Safe Mode allows you to remove any malware in your computer and troubleshoot issues that can’t be fixed when you’re in desktop mode. This is why Microsoft made sure that the Safe Mode option is not available directly and can only be accessed by pressing function keys such as F2, F8 (depends on what PC you are using) or via MSConfig. To make it easier for you to access Safe Mode, this post will guide you on how you can add Safe Mode to the Boot Menu options in Windows 10. As you know, Windows 10 now has Advanced Startup options that allow you to boot directly into Safe Mode without having to restart your PC and then tapping the special key a couple of times. However, if you really have to always use Safe Mode, it’s best to add it in the Boot Menu options. To do that, simply follow the steps below.

• Select Command Prompt (Admin) option from the WinX menu to open Command Prompt with administrator privileges.
• After opening Command Prompt, type the bcdedit /copy {current} /d "Safe Mode" command and hit Enter.
• Once the command is executed, you will see a message saying, “The entry was successfully copied to {74a93982-9486-11e8-99df-00270e0f0e59}”. This message indicates that Safe Mode was successfully added in the Boot menu option which means that you can now directly access it and boot your Windows 10 PC in that mode.

To check if Safe Mode was really added in the Boot menu options, you have to open Msconfig. From there, you will also have to use it to configure the boot settings for the Safe Mode entry. To do so, follow the given steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “MSConfig” in the field and click OK.
• Next, go to the Boot tab and find the Safe Mode option which should be located under the default Windows 10 mode.
• Afterward, you need to select the Sage boot option and Minimal. You also have to select the Make all boot settings permanent option.
• Make sure to increase the timeout to at least 10 seconds which will ensure that the menu does not disappear right away.

Note: In similar steps as above, you can add the Safe Mode with Networking and Safe Mode with Command Prompt entries as well. Just simply select “Network” for Safe Mode with Networking and “Alternate Shell” for Safe Mode with Command Prompt. Once you’re done adding any of them, click on Apply and restart your PC. In addition, if you wish to remove the entry, you just have to open MSConfig again and select the entry you want to remove, and then click Delete.

Libvlc.dll Error Code - What is it?

Libvlc.dll error is a type of DLL file error. Libvlc.dll is a type of Dynamic Link Library file associated with 3rd party software developed by the Videolan Team for the Windows OS. Libvlc.dll file contains small programs similar to EXE executable files which allow multiple software programs to share the same functionality. It helps load and run certain programs developed by Videolan Team on your system. The Libvlc.dll error pops up when the file fails to load and run your desired program. This error is usually triggered during program installation while a Libvlc.dll related software is running on the PC or during Windows start-up or shut down. Libvlc.dll error code may appear on your Windows computer in any of the following formats:

"Libvlc.dll not found." "The file libvlc.dll is missing." "Cannot register libvlc.dll." "Cannot find C:WindowsSystem32\libvlc.dll." "Libvlc.dll Access Violation." "Cannot start Third-Party Software. A required component is missing: libvlc.dll. Please install Third-Party Software again." "This application failed to start because libvlc.dll was not found. Re-installing the application may fix this problem."

Though Libvlc.dll error is not a fatal error code but nonetheless it is advisable to resolve it immediately to avoid any inconvenience.

Solution

Error Causes

Libvlc.dll error code may occur due to several reasons including but not limited to:

• Corrupt Libvlc.dll registry entry
• Malware infection
• Hardware failure
• Deleted or missing Libvlc.dll file
• Another program overwrote the required version of Libvlc.dll

Further Information and Manual Repair

Here are some of the best and easy-to-work-around methods that you can try to resolve Libvlc DLL error on your system in minutes. Let’s get started:

Method 1: Re-install the Deleted Libvlc.dll file

Since DLL are shared files, sometimes the error code may pop up if it is deleted accidentally while uninstalling a program that is also run by the same file. In such a situation, to resolve the Libvlc.dll error all you have to do is re-install the deleted file by going into the recycle bin. If you find it reinstall, but if you don’t then simply download Libvlc.dll file from a reliable DLL file website and install. Hopefully this will resolve the issue. Alternatively, you can re-install VLC which should come with a complete copy of the libvlc.dll. However, if the error code still persists, then try other methods given below.

Method 2: Restore Points - Undo the Recent Changes

Another way to resolve Libvlc dll error is to restore your Windows system to an earlier point. System Restore can return your PC system files and programs back to a time when everything was working absolutely fine. This can help you avoid hours of troubleshooting headaches. This can be easily done by going to the start menu. In the search box type System Restore and press enter. Now click System Restore and enter administrator password if prompted. Follow the steps in the Wizard to choose a restore point and then reboot to activate changes.

Method 3: Repair the Registry

The Libvlc dll error can be triggered by invalid registry entries. To resolve, simply download Restoro. This is a user-friendly and multi-functional PC Fixer embedded with a powerful registry cleaner. It removes all the invalid files, repairs the damaged DLL files, and cleans the registry in seconds. Click here to download Restoro and resolve Libvlc dll error today!

A lot of Windows 10 users prefer the black theme on their computers and when you see anything but black it can get quite annoying. Such as is the case of the Taskbar which, as you know, is usually dark, however, when you take a look at the Cortana search bar, instead of seeing black, you’ll see that it has turned white. To fix this issue, read on as we will provide you some options you can try to set the Cortana search bar back to black. Before you proceed, take note that the options provided below will change all white search boxes to black and that one of these options needs administrative privileges.

Option 1 – Try changing the default App mode

As you know, Windows 10 has two modes, namely the Light and the Dark. Thus, you can switch to the Dark mode so that your Cortana search bar will be black as well. However, remember that it will completely change everything into dark mode so there will be no more Light mode elsewhere.

• First, you need to click on the Start button and then click on the cog icon to open the Windows 10 Settings.
• Next, from the Settings Menu, select Personalization and then select Colours from the left pane.
• Then scroll down until you see the “Choose your default app mode” option and select “Dark”.

After you apply the changes, it will change the Cortana search bar into black instantly. Aside from that, you will also see the User Interface changing into dark mode.

Option 2 – Try changing the Registry value

If you are well-versed in editing registry keys, then you need to try this option. But before you go over the steps below, make sure that you create a System Restore point first so that if anything goes wrong, you can always go back to how it was before the changes were applied.

• Tap the Win + R keys to open the Run prompt.
• Then in the field, type in “regedit” and hit Enter to open the Registry Editor. If a User Account Control prompt appears, just click Yes.
• Now that you’ve opened the Registry Editor, navigate to the following key:

HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionSearchFlightingWhiteSearchBox

• After that, double-click on the “Value” key located on the right pane and set the value to “0” instead of “1” and then click Ok to save the changes made. You should now see a black or grey text box color instead of white.

Option 3 – Try changing the Region

In some forums, a lot of users stated that changing the Region also worked out for them in changing the white Cortana search bar to white. Thus, you need to change the region settings of your computer temporarily. To do so, follow the steps below.

• Type in “Regional Settings” in the box and then click it as soon as it appears from the search results.
• Next, make sure to select a region where Cortana is not available.
• Then select apply to that region. After that, it will change the Cortana search bar color to black.
• Now sign out and sign back in and revert to the original settings. But the changes you made earlier in Cortana will still remain.

Any modifications in a computer, either big ones or small ones can definitely trigger some errors which is why you have to be careful when you modify the system setting. One of the errors you might encounter when you’ve modified your computer is the WHEA_UNCORRECTABLE_ERROR 0x00000124 Blue Screen Error. According to the error data provided by the Windows Hardware Error Architecture or WHEA, aside from system modifications, you could also encounter this error if your computer has a hardware failure which could be due to a hard drive, RAM, or any other hardware component. In most cases, it is related to physical hardware failures which might have something to do with defective hardware, heat-related, memory as well as a processor that is starting to fail or has already failed. To fix the WHEA_UNCORRECTABLE_ERROR 0x00000124 Blue Screen error, here are some suggestions you have to check out.

Option 1 – Try to perform System Restore

Before you further troubleshoot the problem, you might want to perform System Restore first as the BSOD error might be caused by system modifications. Thus, to undo them, you can use System Restore. Run it using these steps:

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

Option 2 – Try disabling Overclocking

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

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

Option 3 – Check your computer’s cooling components and make sure that they are working

It is a known fact that an overheated PC causes system slowdowns and even Blue Screen errors like WHEA_UNCORRECTABLE_ERROR 0x00000124. To fix it, you need to check your computer’s cooling components to see whether they’re properly working or not. Then make sure that you clean them up including the fan and other hardware from dust and other debris.

Option 4 – Use the Windows Memory Diagnostics

Since the problem has something to do with the physical RAM, you need to use Windows Memory Diagnostics. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 5 – Update or rollback or disable concerned device drivers

To fix the WHEA_UNCORRECTABLE_ERROR 0x00000124 error, you can also try to roll back, or update, or disable the concerned device drivers.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers particularly the ones that are under the sections of Keyboard, Mouse, USB, and HID Drivers.
• Next, 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. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions or disable them.

Option 6 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It 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. To run the SFC command, follow the steps given below.

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

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

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

• Reboot your PC.

Option 7 – Try to disable the Digital Driver Signature Enforcement

• Reboot your computer from the Start menu.
• Then select the option while pressing the Shift key. This will open the Advanced Boot menu.
• From there, click on Troubleshoot and select Startup Settings.
• Now select the “Disable driver signature enforcement” option using the arrow keys on your keyboard and then restart your computer normally.

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

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

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• 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 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 5 – Try running the Blue Screen Troubleshooter

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

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

• You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

• After that, save the file and name it “MapDrives.cmd”.
• Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

• Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
• From there, copy and paste the MapDrives.cmd.
• After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

• You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
• After that, open the Task Scheduler and select Action > Create Task.
• Next, type a name and description of the task in the General tab.
• Then click on the Change User or Group button and select a local user group and click OK.
• Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
• From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
• After that, switch to the Actions tab and create a new action then choose to Start a program.
• Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

• And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
• Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
• Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.

If you are one of the few users who is still burning CDs and DVDs, you might have come across an error that says, “Medium Speed Error” or “Power Calibration Error”. There are several factors that could cause this error but it’s most likely that the CD/DVD burner wasn’t able to determine the Optimum Power Calibration rate properly. So what is Optimum Power Calibration rate? It is a test that runs before the burning process to regulate the optimal laser power needed to complete the job. And if this process malfunctions, obviously, you won’t be able to burn the content on your CD or DVD. There are also cases when the Power Calibration error pops up for some small issues that have nothing to do with the regulation of laser power. Here are some quick fixes you can try to resolve the Power Calibration error when burning a CD or DVD.

Option 1 – Make sure you’re using good quality CD or DVD

A lot of burning issues stem down to the purchase of low CDs or DVDs to make sure that what you are using has good quality for it is not always a good idea to purchase cheap products as cheap products could also mean cheap quality.

Option 2 – Try burning at lower speeds

If you’re certain the problem is not with the CD or DVD you are using then you can try burning again, this time at lower speeds. There are instances when doing things quickly can end in a disaster such as the “Medium Speed Error” or “Power Calibration Error” you’re getting.  To fix the problem, you have to burn at a slower speed and just take the time to wait until the burning process is done.

Option 3 – Try updating your burning software

It’s always a good idea to check if the burning software you’re using requires an update especially if it’s throwing up “Medium Speed Error” or “Power Calibration Error”. Thus, you need to update your burning software right away and then try to burn your CD or DVD once the update has been completed.

Option 4 – Try cleaning the disk drive

You might want to consider cleaning the disk drive using several tools in the market that is designed to clean the disk drive. These tools work on removing dust particles from the lens which helps a lot in the burning quality. Aside from that, it also helps in reducing errors like “Medium Speed Error” or “Power Calibration Error”. So give this option a try as it might time for a disk drive cleanup.

Option 5 – Try to disable the IMAPI

If none of the options given above worked, you might want to disable the IMAPI or Image Mastering Applications Programming Interface. How? Refer to the steps below.

• Open Control Panel by simply clicking the Start button and then typing “control panel” in the field.
• Control Panel should pop up in the search results. Once you found it, click it to open it.
• Next, select System Security > Administrative Tools and then click Services.
• After that, you’ll have to search for the “IMAPI CD-Burning COM Service” option.
• Then right-click on it and select Properties.
• From there, switch the Startup Type from “Enabled” to “Disabled”.
• Now click on Apply and then restart your PC.

When you get an igfxem.exe error in Windows, it is not really clear what does this means, usually, Windows throw us some code or we get a DLL error, rarely we get an EXE error. So what does this error means? Intel Graphics Executable Main Module, shortly called as IgfxEM module is a part of the Windows operating system. When you run Microsoft .NET Framework applications that use the AS/400 Data Queue ActiveX control (Mseigdq.dll) to read from and to write to IBM iSeries (AS/400) data queues, you may experience this error. In order to overcome this error and cope with it try the following things:

1. Increase Virtual Memory

   Go to the Start Menu and click on Settings. Type performance. Choose Adjust the appearance and performance of Windows. In the new window, go to the Advanced tab and under the Virtual memory section, click on Change. At the bottom of the new window, check what the Recommended value is and how it compares to Currently allocated. If the current setting is significantly less than the recommended, uncheck the Automatically manage paging file size for all drives box at the top of the same windows and then click on Custom size. Enter the Recommended value in the Initial Size box, and a larger figure in the Maximum size box. Click OK to save the new settings.

2. Download and update .NET framework

   Go to the Microsoft website and download the latest .NET framework. Once the download is complete, install the package following onscreen instructions.

3. Reinstall INTEL graphic drivers

   Go to the intel website and download the latest graphic drivers for your graphic card model. Once the download is complete, install the package following onscreen instructions.

4. Run SCF scan

   If all else fails, run command prompt and inside type sfc /scannow

Blue Yeti has gained popularity among streamers and users that want a high-quality mic for their setup. Without going into details of the hardware itself I will say it is a pretty good mic. Now the issues that have been reported with it are that Windows 11 can have issues with it resulting in the microphone not being recognized by the operating system. If you are one of the unfortunate Blue Yeti users and have this issue, do not despair because we have a solution for you, several to be more precise so you can easily fix the issue and get back to talking.

Check cables

Sometimes it is not a software problem at all. First thing is to check if by any chance cable of the mic is disconnected, damaged, or similar. If the cable seems fine next step is to plug in the mic into another port in order to eliminate faulty jack on the computer. If nothing happened the last thing to try is to connect the mic to another computer so we can be sure that the mic itself is in working order so we can focus on software. If by any chance mic is not working on another computer that some hardware inspection of it will be required.

Set Blue Yeti as a default device

There is a chance that Windows 11 has not set Blue Yeti as a default audio device for recording and therefore you can not use it. In order to eliminate and fix this issue, right-click on the speaker icon on the taskbar in the far-right part of it and choose sound settings. Go down to the input section and pick Blue Yeti beside Choose device for speaking or recording.

Update driver

More often than not device not working is tied to malfunctioning or a bad driver. In order to eliminate and resolve this issue right click on the Start icon and choose device manager. Inside device manager expand the Sound, video and game controllers section. Right-click on each device in the section and choose update driver. Wait for the update to complete and restart your system.

Run the troubleshooter

Press ⊞ WINDOWS + I to open Windows settings. Go to System in the left pane and click on it. In the right panel choose and click on troubleshoot. Inside troubleshoot click on Other. Scroll down and locate the Recording Audio troubleshooter and then click on Run next to it. Wait for the troubleshooter to finish and follow on-screen instructions to resolve the issue.

Check Blue Yeti microphone privacy setting

Not very often, but sometimes privacy settings can be the issue even when everything else is working perfectly. In order to check privacy settings press ⊞ WINDOWS + I to open Windows settings and go to Privacy & Security on the left panel and click on it. On the right panel click on the microphone. Make sure that toggle next to Let apps access your microphone is ON.

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.