Software review series: QuickLook

As you know, Windows 10 comes with the option to create Mobile Hotspot for other devices. This allows you to share your Ethernet connection. However, there are times when one of your devices might fail to reconnect to the mobile hotspot again. For instance, you moved out of the Wi-Fi range because you have somewhere to be and whatnot and when you’re back you find that you are now unable to reconnect to the Windows 10 Hotspot or the shared network. Although you can always restart the mobile hotspot to resolve the problem, however, it might only be a temporary fix. So in this post, you will be given options for a much better solution to the problem. This kind of problem seems unusual and does not occur that often. To fix it, you can try to set up DNS on your Windows 10 device and then configure the settings on the mobile device. It seems that what’s happening here is that the mobile device is unable to lock on to the Mobile Hotspot when the IP address changes for some reason.

Option 1 – Try changing the DNS settings on your laptop

In this option, you need to make sure that IPv4 and IPv6 are selected on your Ethernet connection. You also have to change the Preferred DNS server as well as the Alternate DNS server to 8.8.8.8 and 8.8.4.4, respectively. You also have to validate the settings before you exit just to ensure that you’ve entered everything correctly. After that, open Command Prompt and run the ipconfig command and then take note of the IP address, Gateway DNS 1 and DNS 2.

Option 2 – Try changing the Wi-Fi settings on your mobile device

This option should be mostly the same on all your mobile devices. And given that OEMs build their customization and skin, you might have to fiddle around a little to get the settings. Refer to the steps below to change the Wi-Fi settings:

• Go to the Settings of your mobile device and tap on Wi-Fi.
• Then click the Mobile Hotspot connection that you’ve created on your laptop.
• After that, input the password and tap the Advanced options.
• From there, tap on IP settings and select the Static option instead of DHCP.
• Now you have to enter the IP address, Gateway, DNS 1, and DNS 2 of the laptop you’ve taken note of earlier and that’s it.

Note: If you are already connected to the Mobile Hotspot, long press on the Wi-Fi network and select the Modify Network option and then follow the steps given above to change from DHCP to static. Once you’re done, your mobile device should now be able to connect to the Windows 10 Mobile Hotspot all the time.

Windows 11 has been officially presented during Microsoft’s virtual event on June 24^th. Since presentation internet has been pretty live and busy with a discussion about it, some discussions are positive, some not so much but that is expected and it happens always when a new product is presented. One of information that we have about Windows 11 is tied to the home edition of this OS, Windows 11 home edition will require an internet connection at setup, and a Microsoft account in order to be installed and used. Previous versions of Windows could be installed and used with local accounts but it seems Microsoft has abandoned that idea for its new OS. OS will be delivered mostly as updates or via internet download so internet and online requirement make sense but why it cannot use the local account and must have a Microsoft one is beyond me.

Error 1321 - What is it?

Error 1321 is a Windows PC error. This occurs when you try to install a Microsoft Office suite or program on your PC. The set-up program stops responding and the error message is displayed on the computer screen in the following format:

‘Error 1321. Setup cannot modify the file file_name. Verify that the file exists in your system and that you have sufficient permissions to update it.’

When this error occurs you cannot roll back the installation of the Office Suite or use the Add/Remove program option to remove the installed program.

Solution

Error Causes

Common causes of the occurrence of error 1321 are:

• Encrypt contents to secure data settings are enabled on the folder in which you are trying to install the Office suite/ program.
• PC infected by viruses
• Bad Registry Entries

Further Information and Manual Repair

The good news is that this error code is not fatal and besides it is also easy to resolve. Here are some easy do it yourself methods for you to repair this error on your system in a few minutes:

Method 1: Disable Encrypt Contents to Secure Data

To resolve this error code, make sure the encrypted contents to secure data settings are not enabled. To do so, simply right-click the folder in which you want to install the MS Office Suite or program. Now click properties and then the General tab. Now go to the Advanced option. In the Advanced Attributes dialog box, make sure that the Encrypt contents to secure data check box under Compress or Encrypt Attributes is disabled. If it is not then un-check to disable.

Method 2: Remove Viruses

Viral infection can also trigger error 1321. If this is the reason, then simply install and run a powerful antivirus on your system. An antivirus detects all types of malicious viruses such as malware, adware, spyware, and Trojans. Remove them to resolve the issue.

Method 3: Download Restoro.

If the issue is related to bad registry entries, then it is advisable to download Restoro on your PC. This is a user-friendly and powerful PC Fixer deployed with a registry cleaner. The registry cleaner scans your entire PC and wipes away all the bad entries cluttering and damaging the registry in seconds. Click here to download Restoro and resolve error code 1321 today.

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.

If you aren’t able to pull up any website and instead got the ERR QUIC PROTOCOL ERROR error message in Google Chrome then read on as this post will help you resolve the problem. When you encounter such an error in Chrome, you will see the following error message:

“This site can’t be reached, The webpage at [website URL] might be temporarily down or it may have moved permanently to a new web address, ERR_QUIC_PROTOCOL_ERROR”

This kind of error message pops up when the URL is down. However, if you are certain that the site is not down and you’re still seeing this error message, then troubleshoot further using the suggestions given below.

Option 1 – Try to disable the QUIC Protocol

QUIC is an experimental transport layer network protocol that is present in Google Chrome in order to establish a connection between two endpoints over UDP. So if there is any problem on the development side, you will most likely encounter ERR_QUIC_PROTOCOL_ERROR on your Google Chrome browser when you try to open any website. Thus, you have to disable the QUIC protocol in order to resolve the error. How? Simply follow the steps below.

• Open your Google Chrome browser.
• Now type in “chrome://flags/” in the address bar and hit Enter.
• After that, look for the Experimental QUIC protocol which should be set by default.
• Then expand the drop-down menu and select Disable.
• Restart Google Chrome and see if the error is fixed or not.

Option 2 – Disable VPN

As mentioned, if you are using VPN, this could be the reason why you’re getting the Windows Update error 0x800F0922 so the most obvious thing to do is for you to turn off the VPN and try to run the Windows Update once more. And if you use a VPN software that works using their software, you can just completely exit or log-off from its account. On the other hand, if you are using a built-in Windows 10 VPN, you can simply turn it off or delete all the settings you have created there. Although it’s understandable that you might have to use a VPN connection to connect to the work network, you really have to disable it at least until the Windows Update is no longer stuck in the error 0x800F0922. It would be best if you do this when you are not working.

Option 3 – Disable the Proxy server

You can also try to disable the Proxy server to fix the ERR_QUIC_PROTOCOL_ERROR in Chrome. Refer to these steps to do so:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Windows updates have become a regular occurrence in our digital lives. They are frequent and have become quite necessary. Most of the time they bring us quality content like fixed security, resolved bugs, and even new features but from time to time update itself can be not downloaded properly or it can have some issues when installing. Windows Update Error 0x800F0825 is one of these update errors that will be reported seemingly after applying the update. Altho annoying error it is nothing system breaking and can be easily resolved. Hello and welcome everyone, today we will provide you with solutions on how to resolve error 0x800F0825 when trying to complete a Windows update.

Run Windows troubleshooter

Built-in Windows troubleshooter can help a lot in resolving these issues and we will try it as a first solution because of its simplicity and ease of use.

• Click on START
• Click on settings
• Navigate to Update & Security > Troubleshoot > Additional Troubleshooter > Windows Update
• Click on Run the troubleshooter
• Follow onscreen instructions and let the troubleshooter try to solve the issue

Clear contents of SoftwareDistribution & Catroot2 folders

Altho SoftwareDistribution and Catroot2 folders are essential for the update process it can happen that badly downloaded updates or similar corruption can be stored there and thus producing this error.

• Open file explorer and locate these two folders, go inside and delete content inside them
• Try updating again to see if corruption inside folders was the issue.

Update manually

If the previous two solutions have not produced a result and the error is still present then go to the official Microsoft Update Catalog and download the update manually The catalog is here. Search for updates from the Windows Update Catalog In the Search box, type your search terms. You can carry out a full-text search, using a keyword, KB article, MSRC bulletin, driver manufacturer, driver model, driver version, product, and a classification. Select the appropriate version of Windows. Search or click on Advanced Search if you want to refine your search. A list will be displayed. Select the updates that you want to download. Click Add for each selection to add it to the download basket.

• Download the updates. You may be asked to install an Active-X download control to be able to download files from this site
• Double-click on the downloaded updates to install them

Administrators can download updates from the Microsoft Download Center or the Windows Update Catalog to deploy to multiple computers If you are running Windows Server Update Services (WSUS) 3.0, System Center Essentials (SCE), or System Center Configuration Manager (SCCM) you can import updates directly into these applications. Security updates, critical updates, service packs, update rollups, definition updates, and critical drivers can be configured to synchronize with your server automatically. You can still import these updates into your application by using Microsoft Update Catalog; however, depending on how you configure WSUS, SCE, and SCCM, you may not need to import the updates.

Disable system protection

In some rare cases, antivirus or firewall could interfere with both downloads and execution of certain files. If each previous solution failed disable temporarily your security software and try executing the update again.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

You left your computer to go to the bathroom or to fetch something to eat, maybe you have to answer the phone or open door to a friend and after some time you get back to your computer see the black screen, you move the mouse and it starts to come from sleep slowly. I am the kind of person who gets annoyed by this kind of behavior, I like my PC to be ON all time when I want it to be ON and my power plan on best performance so naturally, I have turned this sleep feature OFF. If you are interested to see how you to can turn off your screen sleeping follow this easy guide.

1. Press ⊞ WINDOWS to open the start menu and click on the settings
2. On settings, screen click on system
3. When the system dialog opens go to Power & Sleep and on the right side change all values to never.

Please note that after each update Windows tend to reset these settings so you will sadly have to return to this after each major update.

Error code 0Xc004F074 - What is it?

Did you previously use Windows 7 or 8 but decided to run with the latest Windows 0S, Windows 10? An early error message encountered was activation error code 0Xc004F074. Error code 0Xc004F074 is manifested when the user fails to activate Windows directly after the installation of Windows 10. This occurs if the previous operating system on your computer was Key Management Service (KMS) activated.

The KMT provides a more seamless operation when users are activating volume license editions of Microsoft Windows and Office. This process tends to be clear to end-users of the system.

Symptoms of error code 0Xc004F074 include:

• Windows is unable to reach your company’s activation service.
• The Key Management Service is unavailable.

Solution

Error Causes

Various factors might incite error code 0Xc004F074. A primary cause is a discrepancy or difference between the KMS client and the KMS host machine. The host computer could possibly be operating a Windows Server 2003 or Windows Server 2008, while the client runs on OS Windows 7 or Windows Server 2008 R2. To supplement, the computer’s time might be a contributing factor. The time on the host machine and client might show a difference (Usually the host time exceeds 4 hours).

Further Information and Manual Repair

To rectify error code 0Xc004F074, users are advised to try various methods. These methods include:

1. Method 1: Update Your KMS Host 9 (Windows Server 2003)

Are you running later versions of Windows Server? Use an update that fixes or installs KMS on your computer. The update is available on Microsoft’s website. Keep clearly in mind that the update is only for Windows Server 2013 Service Pack 1 and later versions of Windows Server 2003.

2. Method 2: Update Your KMS Host 9 (Windows Server 2008)

This step is similar to the aforementioned. However, it applies to Windows Vista and Windows Server 2008. This ensures the service is extended to Windows 7 and Windows Server 2008 R2.

3. Method 3: Update the Time

It was previously mentioned that the time reflected on the KMS host and client might cause error code 0Xc004F074 to manifest. A simple fix to adhere to is to always ensure that the time between both is updated. To Resync the time on the client, execute the following command.

w32tm /resync

4. Method 4: Uninstall the Existing KMS

For this method to be successfully deployed, you’ll need to have in your possession an activation key or KMSpico Key. As you cannot apply the new key with the existing one, remove or uninstall the initial key. To perform this step, open the command prompt. This should be done while the computer is in admin mode. Then, run the command

(slmgr.vbs /dlv)

It should be executed without the brackets and before you have removed the existing key.

After executing the command, you’ll encounter the description:

Windows(R) Operating System, VOLUME_KMS_WS12_R2 channel

Move along with the process by applying the slmgr.vbs /upk to uninstall the existing KMS key.

After the old key is uninstalled, you’re ready to apply the following:

slmgr.vbs /ipk <NewKMSProductKey>

To check if things are in place and complete the process, follow the steps below: PC Settings >Update and Security > Activation

5. Method 5: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

The System32 folder contains vital configuration and information that are essential to the operating system. It is located inside the “Windows” folder and it consists of important DLL files as well as executable files. You probably have noticed some errors that have the “System32” word in them but that does not necessarily mean that the System32 folder is the one that triggers them as these kinds of errors have only occurred when some important files are corrupted or missing. Some users recently reported that each time they start their computers, the System32 folder will automatically open up in the File Explorer. If you encounter the same problem, read on as this post will guide you on what to do to fix it. This kind of issue is most likely caused by service or application interference – it is possible that there is a third-party application installed in your computer or a Windows service that triggers the System32 to pop up during startup. It is also possible that this is a result of system modification. Thus, you need to identify the third-party program or restore your computer to its previous state.

Option 1 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

Option 2 – Perform System Restore

• First, press 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 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the issue. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

 Restart your computer and see if the System32 folder still pops up at startup or not.