Fix Error Accessing the Registry in Windows

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.

Recently, a number of users reported seeing plain white icons on their “.docx” files instead of the Word icon. This kind of issue is mostly caused by a conflict with the default program settings in Windows which is why you may not see any Microsoft Word icon on your .docx files. So if you suddenly find that the Microsoft Word icon is either blank or missing and does not show properly on .doc and .docx document files of Office on your Windows 10 computer, then you can check out the potential solutions outlined below. Before you proceed, you can try to restart your computer as there are instances when a simple system restart can resolve some issues like this one. However, if it does not help, create a System Restore point first. This is to ensure that you can always undo the changes you are about to make in case something goes wrong. Once you have that covered, proceed to the following options.

Option 1 – Try to configure .docx files to open with “winword.exe”

You can try configuring the .docx files to open with the winword.exe in order to fix the problem.

• Right-click on a .docx file and select the “Open with…” option.
• After that, if a prompt appears with a message saying, “How do you want to open this file”, select the “More apps” option to proceed.
• Next, scroll down and check the checkbox that says, “Always use this app to open .docx files” option.
• Then click on the “Look for another app on this PC” link and choose the WINWORD.exe application from one of the following paths based on the installed Office version in your computer and click Open:
  • Word 2016 (64-bit): C:/Program Files/Microsoft Office/root/Office16
  • Word 2016 (32-bit): C:/Program Files (x86)/Microsoft Office/root/Office16

• Now check if you can now see the Word icon on the .doc or .docx files.

Option 2 – Try changing the default Word icon via Registry Editor

• Tap the Win + R keys to open the Run utility.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this path located in the left pane: HKEY_CLASSES_ROOTWord.Document.12DefaultIcon
• From there, double click on the default value at the right pane and based on the Word version you are using as well as the architecture (32 bit or 64 bit) and then copy-paste the corresponding value in the Value data box:
  • For Word 2016 (64-bit) keep it as C:/Program Files/Microsoft Office/root/Office16/wordicon.exe,13
  • For Word 2016 (32-bit) Keep it as C:/Program Files (x86)/Microsoft Office/root/Office16/wordicon.exe,13

• Once you’re done, tap Enter and then close the Registry Editor.
• Restart your computer and see if the problem’s fixed.

Option 3 – Try to rebuild the Icon cache

You may want to rebuild the Icon cache as it could also help fix the issue.

• Tap Win + E to open File Explorer and then click Folder Options and click Views to show Hidden System Files.
• After that, go to C:Users%username%AppDataLocal folder and look for a file named Iconcache.db and delete it.
• Next, go to C:Users%username%AppDataLocalMicrosoftWindowsExplorer.
• From there, look for the following files and delete them.
  • iconcache_32.db
  • iconcache_48.db
  • iconcache_96.db
  • iconcache_256.db
  • iconcache_1024.db
  • iconcache_1280.db
  • iconcache_1600.db
  • iconcache_1920.db
  • iconcache_2560.db
  • iconcache_exif.db
  • iconcache_idx.db
  • iconcache_sr.db
  • iconcache_wide.dd
  • iconcache_wide_alternate.db
• Restart your computer. This will purge and rebuild the icon cache.

Option 4 – Try fixing Office apps

Fixing the Office apps can help you resolve the Word icon issue. All you have to do is open Settings > Apps. From the app list, look for the Microsoft Office Desktop apps and select it and then click on the Advanced options and click Fix. After that, wait until the process is completed and restart your PC. However, if the problem still persists, repeat the steps again but this time, click on Reset instead of Fix.

Option 5 – Try to repair Office Installation

If the options given above didn’t work, you can try to repair the Office installation and see if it can fix the problem.

• Open Control Panel and click on Programs and Features.
• Next, right-click on the Office program that you want to repair which in this case is, Word.
• Select Change and click Repair > Continue. After that, Office will start to repair Microsoft Word.
• Wait until the process is done and then reboot your computer.

Hello and welcome to errortools articles. Today we will talk about some great and awesome tips and tricks for the command prompt. Commands which can make your life easier and your workday more pleasant. That being said let's dive in right into muddy waters and swim out with new knowledge.

Tip 1: Read Motherboard information

There are a lot of reasons why you would like to read information from your motherboard, maybe you would like to upgrade your BIOS, perhaps you would like to know the serial number, maybe even the version number. Well, you can, type the following code into the command prompt and you will receive all information about your motherboard.

wmic baseboard get product,version,serialnumber,product

Tip 2: Copy command output to clipboard

Getting information from the command prompt to a word processor, into an email or any other medium can be somewhat troublesome, usually, people tend to screenshot or write from a command prompt into another destination, which could induce errors, and let's be honest, it is not practical. You can copy command output directly into the clipboard ready for pasting it anywhere with | clip. So for example if you would like to paste the directory structure of your c drive command would look like: dir c: | clip, now output would be placed into the clipboard ready to be pasted anywhere needed.

Tip 3: Erase data permanently

When you delete data on your hard drive, what really happens is that files are marked with a marker which marks that space for new data writing, but the data itself is still present and can be brought back. This sometimes could impose problems but if you would type: cipher /w:c Windows will write random data over each marked file deleting it forever without means to be brought back.

Tip 4: Manage your IP address

If you would like to play with your IP address and do fancy stuff with it do the following: ipconfig /release to release your IP address ipconfig /renew to renew your IP address ipconfig /flushdns to flush down DNS information and enjoy a new browsing start.

Tip 5: Check to see are packets reaching the desired location

You installed a new LAN printer, or a new switch, maybe you want to check if your new site is up and running. Use ping destination in order to see if TCP packets are reaching desired information, you can use it with a specific address like ping 192.168.1.1 or you can type a web address, for example, ping google.com and see if a connection can be established.

Tip 6: Get information about a specific command

So you learned some command prompt commands, but you do not know all of their configuration or switches? No worries, just type command/? to get a list of available switches for it. For example ipconfig/? will write you a list of available switches for ipconfig command.

Tip 7: Link and execute multiple commands one after another.

Let us say that for example, you would like to copy files into a different folder, then rename some and delete others and you need to do a couple of times. Instead of writing command after command once each one is finished link them with && and they will execute one after another.

Tip 8: Scan and repair files.

In order to scan files and repair broke or corrupted ones write in the command prompt: sfc /scannow. Please know that this command can take a long time since it is solely dependant on the number of files, their size, and the power of the computer.

Tip 9: Manage and configure your computer energy

Command powercfg will let you manage and see the power configuration of your computer. Just write powercfg/? and see what you need and want to change or get information about.

Tip 10: Associate files with applications

Windows already has some file associations defined, and some applications take over some type of files but if you want to take control into your own hand use assoc command. For example assoc.txt= "APPLICATION NAME" will associate txt files with the provided application.

Tip 11: Hide files and folder.

Do you have some folder or file with information that you do not want to be seen when someone opens file explorer? Use attrib +h <name of file> and hide file or attrib +h /D <folder name> to hide folder.

Tip 12: Get a list of installed computer drivers

Want to know which drivers are installed in your system? Use driverquery and take a look.

Tip 13: Find and locate shared folders

have you shared a folder but forgot which one and where? Do not bang your head on the wall, we have a simple solution for you. just type in command prompt net share and see everything.

Tip 14: Run commands as an administrator

You do not have administrator privileges? Do you want to bypass common blockades?

runas /user:yourdomainadministrator command

That is all that we have for you today, I certainly hope you have found something useful here and that we have managed to teach you some valuable things.

It has been reported that there are systems out there with Windows 11 operating systems that do not use the whole RAM memory installed in the system. If by any chance you are one of the unfortunate users that has encountered this issue, fear not, we have a solution for you.

Run the Windows Memory Diagnostic tool

1. Press ⊞ WINDOWS + S to open the search menu
2. Type in Windows Memory Diagnostic tool
3. Click on the found app
4. Select Restart now and check for problems
5. Wait for the tool to finish

Memory Diagnostic tool is a built-in tool in Windows, it was designed to automatically find and repair memory issues and should be your first step toward resolving this issue.

Check page file

1. Press ⊞ WINDOWS + S to open the search menu
2. Type in View advanced system settings
3. Click on the search result
4. Click on settings under performance
5. Click on the Advanced tab
6. Click on Change under Virtual memory
7. Uncheck the box for Automatically manage paging file size for all drives
8. Then select the drive and check the No paging file option
9. Click on Set
10. Repeat for all drives on the system
11. Reboot the system for changes to take effect

If after reboot system still does not see and use whole available RAM, repeat this process and turn back ON paging. After you are done move to the next solution.

Modify usable RAM

1. Press ⊞ WINDOWS + S to open the search menu
2. Type in System configuration
3. Click on the search result
4. Go to the Boot tab and click on Advanced options
5. Check the box for Maximum memory
6. Enter the installed RAM on your system in the field box and click on OK
7. Confirm once again on the OK and close the System configuration window
8. Restart the system

If the provided solution has not worked, uncheck the Maximum memory checkbox and save the changes. Move to the next solution.

Change and modify the registry

1. Press ⊞ WINDOWS + R to open the run menu
2. Type in Regedit and press the OK button or hit ENTER
3. Click on YES if prompted by UAC
4. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
5. On the right side find and double click on the ClearPageFileAtShutdown DWORD
6. Enter 1 under Value data and click on OK to save the changes
7. Close the registry and reboot the system

Enable memory remapping inside BIOS

In order to do this fix, you will need to enter BIOS on your system. How entering BIOS is different from system to system depending on your manufacturer, especially if it is a laptop this step you will have to do alone. Go to your motherboard manufacturer or laptop manufacturer and see how to enter BIOS.

1. Enter BIOS (80% of the time this can be done by pressing DEL or F12 while the system is turned ON)
2. Locate System Agent Configuration option
3. Select Memory Remap Feature and Enable it

Your BIOS might be different from ours and you might not have the System Agent Configuration option, in this case, go through the setting and try to locate Memory Remap Feature. If this feature is missing as well move to the next step.

Rearrange RAM modules on the motherboard

Sometimes RAM memory cannot be slotted properly or just purely switching them in slots can solve the issue. Take RAM out, clean memory slots, clean motherboard connectors for them, and place them back in a different order. If by any chance none of the methods worked, then the issue might be in the hardware itself, either memory banks themselves, motherboard, power supply, etc. If this is sadly the case, you will have to locate the issue and replace the faulty part. If you are not technical enough for this adventure, the best solution is to take a PC to a computer repair shop.

Error Code 0xC1900101, 0x30018? - What is it?

Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:

We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.

0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.

Solution

Error Causes

In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:

• Incompatible hardware or driver
• Incompatible security programs or antivirus or incompatible utility software
• A device driver possibly stopped responding to setup.exe while on the installation process.

In some cases, you might be opened to other error messages when attempting to update to Windows 10, including error code 8007002c.

Further Information and Manual Repair

In fixing issues related to error codes, it is best to employ manual repair methods. Using these methods helps users pinpoint the root causes of the issue and apply solutions permanently to fix the issues. While most manual repair methods can be done by every Windows user, even those without technical abilities, there are certain cases where help from a Windows professional is needed. If you’re not up to facing risks in implementing manual methods yourself, consider getting help from a professional Windows technician or you can use a powerful automated tool. In fixing Error Code 0xC1900101-0x30018, you can repeat the same steps used for 0xc000021a (Method One) or you can try doing the following:

• Disable or uninstall your Antivirus program before proceeding to upgrade the system
• Ensure that the machine name is simple (having at least 8 characters) with no special characters like hyphens or dashes.
• Restart the device a few times then try again.
• Disable General USB Devices such as the Smart Card Reader.
• If you use an SCSI hard disk, ensure that you have available drivers you can use for your storage such as a thumb drive and make sure that it is connected. During the Windows 10 setup, select the Custom Advanced Option and use the Load Driver command to be able to load the suitable driver for the SCSI drive. If this fails, try switching to an IDE-based hard disk.
• You can now perform a clean boot. Restart your device then try again.
• If you are using the .ISO file for upgrading the system, you need to disconnect from the Internet first before proceeding to the setup. If you are connected to Wi-Fi or by Ethernet (LAN), make sure to disable both connections then you can proceed to set up again.
• If you’re performing the update through Windows Update, once the download reaches 100%, disconnect from the Internet, and then proceed with the installation.

NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.

• Switch to a local account if the device is connected to a domain.
• Disconnect all external devices attached to the computer such as gaming controllers, printers, or USB keys.

If you’re using Windows Update in installing Windows 10, you can implement the following:

1. Open the Command Prompt window by pressing Windows Key + X. Select Command Prompt (Admin) from the menu.
2. Stop the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

3. Rename the Catroot2 and SoftwareDistribution In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

                        ren

C:WindowsSoftwareDistribution SoftwareDistribution.old

                          ren

C:WindowsSystem32catroot2 Catroot2.old

4. Restart the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. Type Exit in the Command Prompt then close the Command Prompt window then restart the computer.

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

USB ports, just like any other ports, also comes with a power rating. The default power output of a standard USB port is 0.5 amperes and if you notice, mobile phones charge slowly on USB ports which explains why. There are times when Windows may throw an error or warning that says, “Power surge on the USB port”. This kind of error occurs when a connected device tried to draw more power and the error comes as a part of that notification so when you select it, it will say,

“A USB device has malfunctioned and exceeded the power limits of its hub port. You should disconnect the device”.

To easily fix the problem, you can try to disconnect the device and click on Reset and if you click on Close, the port will not work until you unplug it and then restart your computer. On the other hand, if disconnecting the device did not resolve the problem, you can try running the Hardware & USB troubleshooter or use a USB hub. You can also try to reinstall, uninstall or roll back the USB drivers or run the OEM diagnostics. For more information, refer to each one of the potential fixes provided below.

Option 1 – Try to run the Hardware & USB troubleshooter

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Note: You could also try to run the USB troubleshooter as it could also resolve the problem.

Option 2 – Try to use a USB hub

If you’ve encountered the error on a specific device, then it is possible that the device requires more voltage. To fix this error, you can try to use the same device on another computer and if you still got the same error, you might want to use a USB hub that comes with its power source. USB hubs come with high-speed charging ports that should be able to supply the power needed for the device.

Option 3 – Update, rollback or reinstall the Universal Serial Bus Controller driver

If updating the drivers of the device did not fix the “The device is not ready” error, you can try to update, rollback, or reinstall the Universal Serial Bus Controller drivers instead of using the Device Manager. Refer to the following steps:

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

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 4 – Try running OEM Diagnostics if you have any

If the laptop or desktop computer you are using is a branded one, OEMs usually include software to diagnose issues in the computer like the USB port error. So if you have this software, try to run it for diagnosis and use any given suggestions to fix the error.

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

In this post, we will discuss what the “ bootres.dll ” file is in the Windows 10 operating system and where it’s also located. In addition, you will also be guided on how you can replace or fix a corrupt bootres.dll file which may prevent you from booting to your Windows desktop and will display an error message instead saying, “Boot critical file resourcescustombootres.dll is corrupt”. There are times when this error might also boot your PC to the Automatic Repair screen. DLL files, also known as Dynamic Link Libraries are external parts of applications that run on Windows as well as other operating systems. Almost all applications are not complete in themselves and store code in different files so if there is a need for the code, the related file being called by a certain application is loaded into memory and used. If the software or the operating system is unable to find the concerned DLL file or if the DLL file ends up getting corrupted, you will most likely get an error message. In case you don’t know, the bootres.dll file is a critical system OS file, size 90KB, and can be found in the Windows folder. It is a part of the Boot Resource Library and portrays an important role in making sure that your PC boots properly. So if it ends up getting corrupted, your PC may fail to boot correctly and you’ll get an error message instead. To resolve this problem, here are some suggestions that might help. If your PC automatically boots to the Automatic Repair screen, you need to click on that option to run the Automatic Repair. If it doesn’t work, you have to boot into the Advanced Startup options to manually access and run the Automatic Repair. Once you’re in the Advanced Options, you will be able to:

• Run Automatic Repair
• Use System Restore
• Start Windows from an external device
• Access Command Prompt
• And use the System Image Recovery to restore Windows from a Factory image.

If the Automatic Repair fails to fix the problem, you may have to use System Restore or the Command Prompt to carry out further troubleshooting steps. Refer to the guide below to use these tools.

Option 1 – Try running the System File Checker in Safe Mode

Running the System File Checker is the safest way to fix DLL file missing or corrupted errors are thrown up by the Windows operating system as it could give you better results. System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the Machine Check Exception BSOD error. To run the SFC command, follow the steps given below.

• Boot your PC into Safe Mode.
• 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.

Option 2 – Try running the DISM tool to repair the System Image

To repair the System Image, you need to use the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: Dism /Online /Cleanup-Image /RestoreHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Note: The command you executed will check for Windows component store corruption and will restore its good health. The scan might take up to 15 minutes. Once it is done, you have to restart your computer.

Option 3 – Try to repair the MBR and rebuild BCD

To repair the MBR and rebuild BCD, follow these steps: The problem might boil down to the Master Boot Records since the previous case has already been isolated. There are times when the Master Boot Records can get corrupted and even though it is a serious issue, it can still be rectified by repairing the Master Boot Record.

• Tao the F8 key while booting the system to go into the Windows Recovery Menu.
• Next, click on Troubleshoot.
• Then click on the Advanced options to get into the Automatic Repair menu.
• After that, you have to use the bootrex.exe tool, so click on the command prompt and type in the following commands, one after the other:
• bootrec /RebuildBcd
• bootrec /fixMbr
• bootrec /fixboot
• Exit and then go ahead and restart your PC.

Option 4 – Try running the ChkDsk utility

One of the best options you must try is running chkdsk as it will check the disk for any errors and repair them automatically. To use it, follow these steps:

• Boot your PC to the Advanced Options menu and click on Command Prompt.
• Once you’ve opened an elevated Command Prompt, type in the following command and tap Enter to execute it:

chkdsk C: /f /x /r

Note: “C” is the drive root drive so it could be changed if you’re using a different one.

Option 5 – Try resetting your PC

Go to the Advanced Options > Troubleshoot > and select the Reset This PC option from the menu and then select Keep my files.

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

Guide

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

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

What exactly is no audio device malfunction?

No audio device error is among the malfunctions that many Computer consumers run into. No sound or audio can be heard from the computer when the error occurs.

Solution

Error Causes

There are numerous elements that may be the basis of this malfunction. Corrupted or broken sound card drivers, incorrect Device Manager Options for example, or even incorrect BIOS configurations.

Further Information and Manual Repair

How could you recover the standard production of audio by your personal computer and solve this malfunction? Like a number of additional malfunctions, the method of the repair depends on its trigger. To properly solve this dilemma, you are required to run through an evaluation of the pc system so that you can pinpoint the cause. This is because there are numerous variables, which alone, or concurrently may trigger this dilemma. These measures will allow you to work out the no sound device error in your personal computer programs, identify the trigger and fix it. Follow the directions in step 1 if your computer has an onboard audio device installed in it and assess the BIOS settings. You can jump step 1 and move to step two if you utilize a separate sound card.

STEP #1 - Assess the BIOS options.

No sound device error can be caused by incorrect BIOS configurations in your Personal Computer. By fixing these settings if they are the cause of the malfunction, you can easily solve it. Make Sure you restart the pc and immediately access the BIOS options. By locating the Sound card, which is usually known as the AC97 Audio, you should subsequently open the Integrated Peripherals. As soon as you locate it, set it to Allow or Auto. Finally, you should access the On-Board Audio AC97 Control and set it to Allow or Auto as well. If it doesn't solve the situation, proceed to Step Two.

STEP #2 - Analyze the Device Manager

No sound device malfunction can be additionally caused by malfunctions with the Device Manager. To solve this issue, go to My Computer, right-click it, select properties, click on the Hardware tab, then click on Device Manager. At this windowpane, analyze the movie, audio, and game controllers. If you learn that there is a cross on any of the sub things, right-click it subsequently and set it to Enable. The sound card driver may have not been correctly installed or may be damaged if there is Exclamatory Mark or Question Mark on the device manager menu. This does not mean that the sound card driver is ok. It may have malfunctioned even though you do not locate anything unusual. This is because the Device Manager doesn't always recognize errors in audio hardware. After this, you can proceed to step 3.

STEP #3 - Upgrade or reinstall the Sound Card Driver.

About 80% of "no sound system discovered/installed" malfunctions come from broken and/ or out-of-date card drivers. The sound card will not be detected by the Windows Operating System, when the audio card driver is corrupted, damaged, or out-of-date and therefore no sound will be produced by your computer. If this is the cause of the no sound device malfunction, you should reinstall the Audio Card Driver on your computer. Still, you can utilize driver upgrade applications on the web that will help you upgrade out-of-date drivers.