Recovery Tool Zip Repair

[Nikita Desjardins]

Asa follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. The signed Microsoft Recovery Tool can be found in the Microsoft Download Center: =2280386. In this post, we include detailed recovery steps for Windows client, servers, and OS's hosted on Hyper-V. The two repair options are as follows:

Recover from WinPE (recommended option)

This option quickly and directly recovers systems and does not require local admin privileges. However, you may need to manually enter the BitLocker recovery key (if BitLocker is used on the device) and then repair impacted systems. If you use a third-party disk encryption solution, please refer to vendor guidance to determine options to recover the drive so that the remediation script can be run from WinPE.

Recover from safe mode

This option may enable recovery on BitLocker-enabled devices without requiring the entry of BitLocker recovery keys. For this option, you must have access to an account with local administrator rights on the device. Use this approach for devices using TPM-only protectors, devices that are not encrypted, or situations where the BitLocker recovery key is unknown. However, if utilizing TPM+PIN BitLocker protectors, the user will either need to enter the PIN if known, or the BitLocker recovery key must be used. If BitLocker is not enabled, then the user will only need to sign in with an account with local administrator rights. If third-party disk encryption solutions are utilized, please work with those vendors to determine options to recover the drive so the remediation script can be run.

Additional considerations

Although the USB option is preferred, some devices may not support USB connections. In such cases, we provide detailed steps below for using the Preboot Execution Environment (PXE) option. If the device cannot connect to a PXE network and USB is not an option, reimaging the device might be a solution.

Prerequisites for using the boot media

The BitLocker recovery key for each BitLocker-enabled impacted device on which the recover media is used may be required. If you are using TPM-only protectors and using the safe boot option, then the recovery key will not be required. If you are using TPM+PIN protectors, then you may need the recovery key if you do not know the PIN for the device.

Using recovery media on Hyper-V virtual machines

The recovery media can be used to remediate impacted Hyper-V virtual machines. To do so, select the option to generate an ISO when creating the recovery media using the steps above. For non-Hyper-V virtual machines, follow instructions provided by your hypervisor vendor to utilize the recovery media.

Using PXE for Recovery

For most customers, the options listed above or following the steps in the KBs linked towards the end of this post will help restore your devices. However, if devices are unable to use the option to recover from USB, for example, because of security policies or port availability, IT admins can use PXE to remediate.

To use this solution, you can use the Windows Imaging Format (WIM) that the Microsoft Recovery Tool creates in an existing PXE environment as long as the impacted devices are on the same subnet as the PXE server. Alternatively, you can either use the PXE server approach outline below. This option works best when the PXE server can be moved subnet to subnet easily for remediation purposes.

The Microsoft Support and Recovery Assistant works by running tests to figure out what's wrong and offers the best solution for the identified problem. It can currently fix Office, Microsoft 365, or Outlook problems. If the Support and Recovery Assistant can't fix a problem for you, it will suggest next steps and help you get in touch with Microsoft support.

Below are some of the frequently known issues that our users face. To resolve any of the problems listed below, simply click on the recommended solution for the associated problem to get started. The link will take you directly to the solution in Microsoft Support and Recovery Assistant application.

To enhance the support for Microsoft 365 customers and eliminate the requirement to download the Support and Recovery Assistant, we are integrating Microsoft Support and Recovery Assistant diagnostics directly into Get Help, a built-in Windows feature. Get Help provides a broader range of diagnostics, ensuring Microsoft 365 customers receive the most effective solutions for their issues.

The Support and Recovery Assistant offers automated fixes for many of the issues it detects. If you elect to perform an automated fix, the recovery actions that are performed by the fix are entered into the log file created by the Support and Recovery Assistant. To view this log file and the recovery actions performed during a scenario, please follow these steps.

Yes. If you're an administrator and want to install and start the Support and Recovery Assistant from a shared location on a network instead of the default internet location don't use the download link in this article. Instead, follow the steps in this article on docs.microsoft.com: How to install and maintain Microsoft Support and Recovery Assistant (SaRA) from a network share .

Yes. We now have the capability to run Support and Recovery Assistant scenarios using a command-line. For more information, read this article on docs.microsoft.com: Enterprise version of the Microsoft Support and Recovery Assistant.

We're sorry, but we don't have a version of the Support and Recovery Assistant that can be installed on a Mac. However, the Outlook for Mac scenario in the app can troubleshoot some issues that occur on your Mac even though the app is installed on a Windows PC.

When you reach the end of a scenario in the app you're shown a screen where you're asked if we fixed your problem. Select any of the top three options to have the remaining questions in the screen displayed. You can enter your feedback into the box at the bottom of the screen.

When you run the Support and Recovery Assistant to identify or diagnose a particular issue, the tool records anonymous information (Telemetry) about the actions and analysis that are performed by the tool when a scenario is run. Microsoft uses the telemetry data to improve customer experiences and to monitor the health of the application. The amount of telemetry data collected differs with different scenarios.

The log files include comprehensive information such as SessionID, TimeStamp, and Office applications on the affected system. The collected information is completely anonymous, and it does not trace back to you in any form. The following is the definition of some fields that are collected as part of the telemetry data:

The Inbox Repair tool doesn't connect or analyze any data stored in an Exchange mailbox. The tool only looks for errors (corruption), and if there are any, gives you the opportunity to allow the tool to fix those errors. If you can't start the Inbox Repair tool, you should try to repair your Outlook program.

In the Folder Pane, you might see a folder named Recovered Personal Folders that contains your default Outlook folders or a Lost and Found folder. Although the repair process might recreate some of the folders, they may be empty. The Lost and Found folder contains any folders and items recovered by the repair tool that Outlook can't place in their original structure.

You can create a new Outlook Data File and drag the items in the Lost and Found folder into the new data file. After you've moved all the items, you can remove the Recovered Personal Folders (.pst) file, including the Lost and Found folder. To create a new Outlook Data File, see Create an Outlook Data File.

If you can open the original Outlook Data File, you might be able to recover additional items. The Inbox Repair tool creates a backup file with the same name as the original, but with a .bak extension, and saves it in the same folder. There may be items in the backup file that you might be able to recover that the Inbox Repair tool couldn't.

When your computer is unable to boot to the operating system even after repeated attempts, SupportAssist OS Recovery automatically starts. This recovery environment enables you to diagnose hardware issues, repair your computer, back up your files, or restore your computer to factory defaults.

If your computer does not support SupportAssist OS Recovery, you can download the operating system recovery image. Learn How to Download and Use the Dell Operating System Recovery Image in Microsoft Windows.

Important: If the recovery image on the hard drive is corrupted or deleted, the computer cannot boot to the recovery environment. Newer Dell computers support BIOSConnect, a feature that allows you to restore the recovery image on the hard drive. Learn more about Using BIOSConnect to recover SupportAssist OS Recovery Partition.

Reset to Factory Settings: This option restores the original factory-installed operating system and software that was shipped with the computer. The local recovery image is available only on consumer platforms such as Alienware, Inspiron, Vostro, and XPS products.

To restore your Dell computer using the SupportAssist OS Recovery Cloud option, you must create a USB recovery media using the Dell OS Recovery tool. Follow the steps below to create the USB recovery media.

Reset to Factory Settings: This option restores the original factory-installed operating system and software that was shipped with the computer. The local recovery image is available only on consumer platforms such as Alienware, Inspiron, Vostro, and XPS products.

one of our laptop use efde. when the efde start to encrypt the user feel the laptop became slow and try to restart (according to the console, this user encrypt the disk in less than 10% before restart).

3a8082e126