Your computer has lost the lease to IP Address

As you know, games with good graphics and fast play are definitely resource-intensive and can consume a lot of storage space on your computer. Because of that, they have to be compressed before it gets downloaded to your computer and then unpacked to the hard drive before it gets installed. However, if an error occurs in your computer’s RAM during the installation process or if your hard disk does not have enough memory to handle the process, then you might encounter the isDone.dll error which states:

“An error occurred when unpacking, Unarc.dll returned error code -1, ERROR: archive data corrupted (decompression fails).”

If you encounter the isDone.dll error message on your Windows 10 computer, then read on as this post will show you how you can fix it. This error has something to do with the incomplete installation of PC games or files of larger size. The ISDone.dll error appears due to faulty Unarc.dll file residing in the System32 folder on 32-bit operating systems and the SysWOW64 folder on 64-bit systems. So, if you see this error message, then, it means your computer was not able to read installation archive files.

What is Unarc.dll file?

Unarc.dll is a dynamic link library for Windows. Some applications or games require this file to function properly. So, if it goes missing or, an error occurs when you start a game or an application, you may get various kinds of errors. ISDone.dll error while playing games on PC

Option 1 – Try to reinstall the game

The isDone.dll error could also be caused by the installation of an unknown application. Or it could also be caused by an outdated or corrupted application. In other words, if the game you are trying to install is broken or corrupted, then it’s no wonder why you’re getting the isDone.dll error. To fix this, make sure that you download the latest updated version of the game and then try to install it again and see if the problem is resolved or not.

Option 2 – Try to re-register the .dll file using the Regsvr32 tool

• The first thing you have to do is to locate the DLL file named dll on your computer and rename it to Unarc-bak.dll.
• Next, copy the Unarc.dll file from another well-functioning computer and save it on your desktop.
• After that, move the DLL file you just copied to the System32 folder if you are using a 32-bit operating system, or the SysWOW64 folder if you are using a 64-bit operating system.
• Now you have to register the new DLL file and you can do that using Windows PowerShell.
• Open Windows PowerShell and then execute this command if you have placed the DLL file in the System32 folder: regsvr32 %systemroot%System32unarc.dll
• On the other hand, if you have placed the DLL file in the SysWOW64 folder, then execute this command: regsvr32 %systemroot%SysWOW64unarc.dll
• Once you’re done, a message will be displayed saying that the DLL file was registered.
• Restart your computer and check if the problem is now fixed.

Option 3 – Troubleshoot the isDone.dll error in a Clean Boot State

You can also troubleshoot the isDone.dll error in a Clean Boot state. It could be that there are some third-party applications in your computer that're preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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 you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 4 – Try updating or reinstalling your Graphics drivers

Updating or reinstalling the Graphics drivers in your computer can also help in resolving compatibility issues between the operating system and the driver that might have caused the isDone.dll error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 5 – Try scanning your computer using Windows Defender

The isDone.dll error might also be infected with malware or virus and to eliminate it, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

There has been recently discovered in the field of malware targeting Android devices. Affecting more than 10 million users of Android phones, the malware GriftHorse is doing its attacks via phishing and premium services scams. A lot of applications have been discovered that are hosts for this malware and many of them are inside the Google store and available for download. According to Zimperium zLabs, this malware that was recently detected has been doing its scams and attacks even in November of 2020 and has thus far accumulated hundreds of thousands of dollars in its scam. On the surface it looks very harmless, asking for typical permissions like internet access, calls, and other related needed functions, and then it waits. After few months the real attack happens when users get charged with premium service they never subscribed to in the first place.

List of Infected Applications that Carry GriftHorse Trojan

Zimperium zLabs listed out some of the apps with this malware. Users are advised to avoid installing them.

•     Amazing Video Editor
•     Bag X-Ray 100% Scanner
•     Bus – Metrolis 2021
•     Call Recoder Pro
•     Call Blocker-Spam Call Blocker
•     Cinema Hall: Free HD Movies
•     Coupons & Gifts: InstaShop
•     GPS Phone Tracker – Family Locator
•     Fingerprint Changer
•     Fitness Point
•     Free Calls WorldWide
•     Geospot: GPS Location Tracker
•     GPS Phone Tracker – Family Locator
•     Handy Translator Pro
•     Horoscope : Fortune
•     iCare – Find Location
•     iConnected Tracker
•     Instant Speech Translation
•     Lifeel – scan and test
•     My Chat Translator
•     My Locator Plus
•     Plant Camera Identifier
•     Racers Car Driver
•     Safe Lock
•     Screen Mirroring TV Cast
•     Slime Simulator
•     Smart Spot Locator

These are only some of the many infected apps available on the internet. Zimperium zLabs also warned that GriftHorse Trojan exists in over 70 countries worldwide. The infected app quickly changes the language and displays content depending on the user’s IP address.

Mapping network drive has many benefits in terms of speed and ease of access of files via network. It lets you access the hard drive over the whole network like it was the hard drive inside your PC case. In order to easily and quickly map a folder as a network drive follow the guide below.

1. Open File Explorer
2. Click on the three dots icon in the Toolbar
3. Select Map Network Drive
4. Click the Drive drop-down menu
5. Select a driver letter that you wish to assign as a network drive
6. In the folder field enter network device and share name (click on browse to see all devices on local network)
7. Check the box beside Reconnect at sign-in if you wish to automatically connect to a network drive on Windows startup
8. Check Connect Using Different Credentials if you wish to connect to a network drive using different credentials that one used to login into Windows.
9. Click Finish

After finishing setting Windows 11 will try to connect to the network drive and if successful drive icon will appear inside File Explorer and the drive will open up to see its content. If for any reason it cannot connect try checking user credentials, cables, network adapters, etc.

Error Code 0x8007007e – What is it?

Error code 0x8007007e often occurs when users attempt to use Windows Update but are unable to access updates or webpages. To resolve this issue, you will need to use tools that detect and correct corrupted files as this is usually the main reason for the error.

Solution

Error Causes

Once this error code is encountered, it's a clear indication that your Operating System has malfunctioned. This could be a consequence of an incorrect or failed installation of software. The software might leave invalid entries in the Windows registry. Improper shut down of your system and a malware attack are also causes of error code 0x8007007e. Additionally, someone with little or no technical knowledge might have deleted a system file by accident. Missing system files can also equate to other error codes such as registry error code 19.

You may not always be able to prevent issues from affecting your computer, but proper measures can be taken to limit your risk of experiencing problems like error code 0x8007007e. See the following suggestions below:

• Ensure proper system maintenance by regularly using your automated tool. This will ensure your system is in good shape and error-free. It will also clean your system regularly leading to a boost in PC performance
• Keep antivirus software up-to-date. Antivirus software if crucial for the proper functioning of your computer. Keeping your antivirus updated is one of the best ways you can avoid problems with your PC.

Further Information and Manual Repair

Method One: System File Checker

System File Checker is a Windows tool that allows users to check their system for corrupt or bad system files. The utility scans for corrupt files and repairs them as well as files that may have gone missing.

Depending on the type of Windows operating system on your computer, you may need to follow varying instructions. However, note that Windows operating systems including Windows 10 and Windows 8 or 8.1 and Windows Vista all provide access to System File Checker via Command Prompt.

Once you run System File Checker, the tool should be able to repair and replace corrupted files. However, in cases where the repair process does not take place, you can attempt a manual repair by replacing the corrupt file the tool identifies with a good file. The process may require technical knowledge of Command Prompt so consider help from a Windows repair technician or consider contacting Windows for instructions based on your computer’s operating system.

Method Two: Run System Restore Tool

The System Recovery Options menu in Windows contains many tools which can enable users to resolve serious errors. In the case of Error Code 0x8007007e, one of the best tools in this menu is System Restore.

When an error occurs which inhibits users from accessing key functions on their system, System Restore enables the user to restores the computer to an earlier period without causing harm to files, photos, or documents.

However, once you run this tool, you will only be able to access files available within the period to which your computer is restored. For this reason, carefully consider which period is best suited to your purposes. Also, ensure you restore the system to a time when error code 0x8007007e was not present on your machine.

If System Restore does not resolve the error, you may undo the restoration changes. Ensure you have sufficient free space on your machine hard disk before you proceed (300 MB at least for hard drives above 500MB or at least 50 MB for smaller sized disks).

Method Three: Download Automated Software

When it comes to resolving error codes, it can often be a frustrating and tricky venture, especially when you are attempting to fix the problem manually. The Internet is awash with bits and pieces of instruction, some misleading at best with uncertain success rates.

But what if there was a one-stop-shop or better yet a tool that offered solutions for error codes including 0x8007007e?  Download a powerful automated tool that offers easy and effective, user-friendly solutions for users with varying error code problems.

TPM or Trusted Platform Module version 2.0 is a must-have if you plan on upgrading your system to Windows 11. So what exactly is TPM and do you have it?

What exactly is TPM?

TPM is a tamper-resistant hardware technology tasked with generating and storing encryption keys inside it for better PC security. It can be remotely used to authenticate hardware and software by utilizing a unique endorsement key placed into the hardware itself. This technology can be used for example in BitLocker inside Windows in order to have data on a hard drive encrypted so if the mentioned drive is connected to another computer it would not be able to be accessed since the encryption key is stored in the TPM module. Microsoft is pushing its agenda that Windows 11 must be and must feel like safety first OS which will protect user data and user information and requiring TPM means that each Windows 11 will be secure so no additional software patches will be required for an extra layer of security. Windows 11 will assume that each user has TPM encryption enabled and will be built upon that.

Do you have TPM on your computer?

If your computer or hardware has been purchased in 2016 or later there are very high chances that you already have the required technology to run Windows 11. Unfortunately, many gaming motherboards have not been placing TPM in their boards and you might not have it. Also, there is the option of you having it but it is turned off in motherboard settings making Windows unable to detect it. As you can clearly see there are a lot of scenarios around required tech and honestly it is a complete mess. But lucky for you there are ways to find out do you possess the needed module in order to make an upgrade. On your current computer on which you would like to make an upgrade in your current Windows OS press ⊞ WINDOWS + R to open the run dialog. Inside run dialog type in TPM.msc and press ENTER to open Trusted Platform Module Management on Local Computer. You will immediately receive information do you have the required module. If everything is fine, you are good to go, however, if it says that compatible TPM cannot be found there is a chance that either you do not have needed hardware or it might be turned off inside motherboard settings.

Check motherboard UEFI

If you have a newer motherboard but Windows utility cannot detect TPM there is a chance that it might be turned off directly on your board. In order to check this, you will have to boot up your PC into UEFI either by pressing the corresponding key when it is turned ON or from Windows reboot options. Once you are inside UEFI you need to find security options and see if there is an option to turn ON or enable TPM. Since every motherboard is different and has different UEFI software we cannot cover all of the permutations and the best we can do is hope that provided information is enough. You can also visit your motherboard manufacturer to see instructions for your specific case.

Conclusion

TPM itself is generally an OK idea and I can surely see good sides of it but there is this lurking feeling that generally, Microsoft is not really concerned about the security of our data and that the real requirement for this is trying to battle software piracy. I simply cannot trust company which introduced tons of telemetry tracking through ages and which has done everything in their power to battle non-legal use of their software. I do not promote piracy but I support free choice and besides, who can tell me what will happen if TPM malfunctions, will I lose all of my data forever? It is not so uncommon that TPM has malfunctioned in the past and it is only logical to presume it can do it again in the future but this time we will not have the choice not to use it, we will be forced into it.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

Error Code 0x80070057 – What is it?

Error code 0x80070057 occurs when Windows users are having problems installing updates on their machines. The error code may result due to issues affecting Windows Update, for instance, problems with system files or settings that can be accessed or modified using the registry in Windows. Error code 0x80070057 affects multiple versions of the Windows operating system including Windows 10. Common symptoms manifested when this error code and other update error codes occur include the following:

• Inability to complete the installation of updates via Windows Update
• Presence of error code message box

Error Causes

Update error codes like error code 0x80070057 occur when there are issues related to system files, programs or malicious software is present on one’s machine. To combat these issues, users may need to implement manual repair procedures, depending on the specific error code present on their device.

Solution

Further Information and Manual Repair

Windows users can fix error code 0x80070057 by manually repairing or deleting subkeys and values within the Windows registry. This enables Windows Update to function as the proper modification of settings and other information present in the registry can fix problems associated with certain error codes.

The manual repair procedures also enable users to address specific problems on the devices that may not be fixed through the use of other methods.

Method One: Back-Up Registry in Windows

The Windows registry contains information regarding applications installed on the version of Windows you use on your device. This information as well as settings related to hardware are all accessible to users and can be useful when combating problems like error code 0x80070057.

However, users will need to be very careful when making modifications within the registry in Windows. This is due to the fact that errors made while accessing the registry can lead to serious issues on your PC. Backing up your registry before you modify it is crucial since it will provide protection against any problems that may arise if you make an error. This is the first step in resolving error code 0x80070057. Follow the steps below to back up your registry properly.

• Step one: Type regedit.exe in the search box near the Start button.
• Step two: Type the appropriate password or provide confirmation if you are prompted to do so
• Step three:  Locate Registry Editor
• Step four: Select registry key or subkey that you want to back up
• Step five: Click File > Export
• Step six:  In the Export Registry File dialog box, choose a location where you will save the backup copy
• Step seven: Name the backup file then select Save.

In the case of fixing error code 0x80070057, the registry file or subkey you will need to back up relates to this: HKEY_LOCAL_MACHINE. This contains configuration details or information related to your machine regardless of the user. Also note that the registry, once you have created a backup file, will be protected, thus enabling you to move to the manual method mentioned below.

Method Two: Make Changes to the Windows Registry

The execution of modifications to the registry can be a complex procedure, especially if you are an average Windows 10 user who lacks technical knowledge. Thankfully, even non-technical users can access the solutions they need by simply following the instructions provided in this article.

You may also contact a Windows repair technician as well, in case you have trouble implementing the steps mentioned for modifying your Windows registry or if other problems arise while you are proceeding with these instructions.

Step one: Access the Windows Registry Editor by typing regedit.exe in the search box near the Start button.

Step two: Type the appropriate password or provide confirmation if you are prompted to do so

Step three:  Locate Registry Editor

Step four: Enter the following:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsUpdateUX] "IsConvergedUpdateStackEnabled"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsUpdateUXSettings] "UxOption"=dword:00000000

After making these modifications in the Windows registry, restart your machine. You can then check Windows Update to see if the problem has been resolved. If the modifications to the registry have proven successful, you will no longer see the error code 0x80070057 message box. You will also be able to complete all updates via Windows Update.

Method Three: 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.

Error 0x800CCC90 - What is it?

Error 0x800CCC90 is a typical Outlook error. This error indicates that Outlook has failed to connect to the mail server that handles and manages the incoming and outgoing emails. The error message is displayed in the following format:

“There was a problem logging onto your mail server. Your User Name was rejected.”

This error limits your ability to send and receive emails on Outlook. If you largely communicate at the workplace using your Outlook account, this error may slow down your work productivity and performance dramatically. Therefore it is advisable to fix it immediately.

Solution

Error Causes

The error 0x800CCC90 is triggered several reasons including but not limited to:

• Authentication issues
• Failure of POP 3 Server
• PST File Corruption
• Registry issues- Invalid Entries
• Viral infection

Further Information and Manual Repair

To resolve error 0x800CCC90, try the methods given below:

Method 1 - Adjust the Authentication Settings

To resolve the error 0x800CCC90, adjust the authentication settings. Here’s what you need to do:

• First, go to the ‘Tools’ tab and select the ‘Accounts’ option.
• Once you select the account option, an internet accounts box will appear on the computer screen.
• Simply double click on the account property box after that go to the server tab and click on it.
• Check the box that says ‘My Server Requires Authentication’.
• Click on apply to accept changes tab to save changes and close the window.
• To activate changes made, restart Outlook and then try sending emails again.

Method 2 - Download a PST Repair Tool

If the error is triggered by PST file corruption, then the best way to resolve it is to download the PST repair tool. Download the PST repair tool from a trusted website. Run it on your system to fix PST file issues and resolve error 0x800CCC90.

Method 3 - Scan for Viruses

Another way to resolve this error is to scan for viruses. Viruses usually enter computer systems through phishing emails or while downloading attachments. You may not know this but viruses may be affecting your PC. Due to viruses, errors like error 0x800CCC90 can also be triggered. Therefore install an antivirus to scan and remove errors on your PC.

Method 4 - Clean the Registry and Remove Invalid Entries

Due to poor PC maintenance, misconfigured and invalid registry entries may be stored in the registry. Such entries may lead to Outlook errors too. Thus to resolve you must clean the registry and remove these entries right away. Download a registry cleaner to fix the error. Whether the error is triggered by viral infection or registry issues, it is recommended you download only Restoro. This is the one-stop solution to resolve all PC related errors. This software is deployed with 6 scanners including a registry cleaner, an antivirus, and a system optimizer. It is user-friendly and has simple navigation. It is compatible with all Windows versions. In just a few clicks this software resolves practically all types of PC-related errors including error 0x800CCC90. Click here to download Restoro today!

If you encounter an error saying, “error accessing the registry” when you try to merge a registry key on your Windows 10 computer, you’re not alone as some users also experienced the same problem. According to these users, they encounter the error after they’ve re-installed their Windows version and tried to open a .reg file. Based on the reports, this error could occur if the registry file does not have administrative privileges. Meaning to say, the program does not have the necessary permission to merge the .reg file. This is common with fresh installs as well as reinstalls. Moreover, this kind of issue could also occur due to system file corruption. Whichever the case may be, here are some troubleshooting tips you can check out to resolve the error.

Option 1 – Try to import the .reg file with admin privileges

As pointed out, the error may be due to a lack of admin privileges. It could be that the Registry Editor does not have admin privileges to merge the registry file. This is common with new Windows installations especially since the Registry Editor hasn’t been opened before. So you need to import the .reg file again and this time, with admin privileges.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap the Ctrl + Shift + Enter keys to open the Registry Editor with admin privileges.
• A User Account Control or UAC prompt will appear where you have to click Yes to proceed.
• After opening the Registry Editor, go to File > Import using the ribbon bar at the top.
• Next, use the import menu to go to the location of the file you were trying to merge. Once you’ve found it, click Open to merge it with your current registry. This should fix the problem. If not, refer to the next options below.

Option 2 – Try performing a System Restore

Running System Restore can also help you fix the error when accessing the Registry. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

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

Option 3 – Try to perform repair install by creating a Windows 10 installation media

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try running the System File Checker Scan

As mentioned, the error when accessing the Registry might be caused by file corruption. And that’s where the SFC scan comes in. The SFC or System File Checker scan could detect and automatically repair damaged system files. 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. 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.

• Now restart your computer.

A newfound bug in Google docs is causing it to crush and upon reopening it will crush again making it very difficult to re-access your document. The bug is manifested when a series of the same word is typed into a document and Show grammar suggestion is turned on.

How was it found

A Google Docs user, Pat Needham brought up the issue on Google Docs Editors Help forum.

"I've only tried in Google Chrome, with documents from three separate Google accounts (personal, G Suite Basic, and work one which might be enterprise). All three experience this same issue".

"It's case-sensitive. So trying with 'and. and. And. and. And.' doesn't cause it to crash."

While Needham publicly reported the bug, it appears that the issue was discovered by Eliza Callahan who was writing a poem novel for her novel using Google Docs.

Needham's findings have also been confirmed by other users running Firefox 99.0.1

Another user, Sergii Dymchenko, said strings like "But. But. But. But. But." triggered the same response. Some also noticed putting any of the terms like "Also, Therefore, And, Anyway, But, Who, Why, Besides, However," in the same format achieved the outcome.

A YCombinator HackerNews reader suspected the cause to be the "Show grammar suggestion" option in Google Docs.

A Google spokesperson confirmed the presence of the issue adding, "we're aware of this issue and the team is working on a fix."

How to recover your document

First thing first, turn off Show grammar suggestions so you do not run into issue by accident. In order to turn it off go to Tools and then into Spelling and grammar and untick Show grammar suggestions.

Now, if you already have a document that has been crushed, fear not because there is a workaround to access it. For some strange reason this bug does not manifest on Google Docs mobile app, so you can open the crushed document in the mobile app, delete words that have caused the bug and reopen the document on your desktop.

Until Google comes up with the solution this is currently the only way to address the issue.