# Disk Recovery Procedure, What File Type Is Needed?

**URL:** <https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195>\
**Category:** General\
**Created:** [October 22, 2026, 2:57pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195 "2026-10-22T14:57:20Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bran21](https://avatars.discourse-cdn.com/v4/letter/b/7ab992/32.png) [@bran21](https://tech-community.robotics.abb.com/u/bran21)\
**Post date:** [October 22, 2026, 2:57pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/1 "2026-10-22T14:57:20Z")

</div>

Hi,

I am trying to use the **Clean Disk** function in RobotStudio’s Installation Manager (RW6) to completely reset a 2GB internal SD card from an IRC5 Compact controller. (due to a failed upgrade and stuck in disk full and cannot create nor delete any of the systems etc.)

I am following the standard recovery disk procedure, but after I click “Write Disk” and select “No” for the product defect report, **I never get the prompt to insert the SD card.**

Instead, I get the message:  
_“One or more products were not found. Please browse for product directory!”_ (what file is it looking for?`).

 ![filetoselect](https://europe1.discourse-cdn.com/flex005/uploads/robotics1/original/2X/8/8cc57783b1c55cfdcd2c6d10e79ad179fa8559db.png)

I have the RobotWare files saved locally on my PC and navigated to the folder containing `RobotWare_RPK_6.16.3007` in the browser panel, but not sure if this is right file to select or if it should be a ‘boot’ file etc.

Which exact folder, package, or file type do I need to select in this window so RobotStudio can find the necessary files, and ‘clean’ the SD card?

Thank you for any insight!

---

<div class="post-metadata">

**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\
**Post date:** [October 23, 2026, 2:14pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/2 "2026-10-23T14:14:15Z")

</div>

Look here:

C:\Users\“your\_user\_name\_here”\AppData\Local\ABB Industrial IT\Robotics IT\RobotWare

---

<div class="post-metadata">

**Author:** ![bran21](https://avatars.discourse-cdn.com/v4/letter/b/7ab992/32.png) [@bran21](https://tech-community.robotics.abb.com/u/bran21)\
**Post date:** [October 23, 2026, 2:34pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/3 "2026-10-23T14:34:14Z")

</div>

I managed to resolve this issue with some help. In RobotStudio 2024/2026, the directory structure for RobotWare distribution packages has changed, causing the tool to fail to auto-locate the paths.

**How to fix it:**

1. Open the **Robot Recovery Disk Creator** and look at the upper panel.

2. Select the **BootServer** line item and completely remove the default path that is currently filled in.  

3. Keeping the BootServer line highlighted, use the lower file browser panel to manually navigate to the new `DistributionPackages2` directory path:  
`C:\Users\....\AppData\Local\ABB\DistributionPackages2\ABB.RobotWare-6.xx.xxxx\RobotPackages\RobotWare_RPK_6.xx.xxxx`

4. Once you target this specific **RobotWare\_RPK** folder, the tool will recognize it, unlock the button, and allow you to successfully run the **“Clean Disk”** procedure.

Thank you to Luis from tech support!

---

<div class="post-metadata">

**Author:** ![bran21](https://avatars.discourse-cdn.com/v4/letter/b/7ab992/32.png) [@bran21](https://tech-community.robotics.abb.com/u/bran21)\
**Post date:** [October 23, 2026, 2:48pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/4 "2026-10-23T14:48:43Z")

</div>

# After the “Clean Disk” procedure, what are the next steps?

 ![cleaned disk](https://europe1.discourse-cdn.com/flex005/uploads/robotics1/original/2X/6/65ef3913aba7155042e91a27afc15cb513231450.png)

Now that the SD card has been successfully cleaned, I want to make sure I follow the exact required procedure for reinstallation and avoid skipping any critical steps.

Are the following steps correct to get the system back up and running?

1. **Hardware Reinstallation:** Leave the IRC5 controller powered off, insert the “cleaned” SD card back into its original slot in the controller, and then turn the controller power back on.
2. **Connection:** Connect my laptop directly to the IRC5 controller cabinet using an Ethernet cable plugged into the **Service Port (X2)**.
3. **System Deployment:** Open RobotStudio, navigate to the **Controller** tab → **Installation Manager** , select **Create New** , and choose **Create a New System** (or create from an existing Virtual Controller layout) to deploy the software back to the robot.

Is it safe to proceed with this sequence, or are there any specific pre-requisites or calibration steps I need to watch out for during this initial boot?

I appreciate any guidance or verification on this process!

Thank you!

* * *

---

<div class="post-metadata">

**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\
**Post date:** [October 23, 2026, 3:22pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/5 "2026-10-23T15:22:45Z")

</div>

Have you already created this system with installation manager? If so, you should just need to download it. Otherwise, with create new, you need the keystrings.

---

<div class="post-metadata">

**Author:** ![bran21](https://avatars.discourse-cdn.com/v4/letter/b/7ab992/32.png) [@bran21](https://tech-community.robotics.abb.com/u/bran21)\
**Post date:** [October 26, 2026, 12:16pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/6 "2026-10-26T12:16:19Z")

</div>

> [@lemster68](#):
>
> Otherwise, with create new, you need the keystrings.

Does that mean I will just need to upload the license file during the ‘create a new system’ process?

_ **UPDATE** _: I just reinserted the SD card back into the robot controller, physically connected to controller → opened installation manager RW6 → Created a new system → Added my old license file that I found within ‘backinfo’ from an old backup that I had.

It seems to be a fresh system now and have to update the rev counters etc!

Thank you!

---

<div class="post-metadata">

**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\
**Post date:** [October 26, 2026, 2:11pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/7 "2026-10-26T14:11:17Z")

</div>

Yes, you will need to include the system keystring and the drive module key while creating the new system.

---

<div class="post-metadata">

**Author:** ![bran21](https://avatars.discourse-cdn.com/v4/letter/b/7ab992/32.png) [@bran21](https://tech-community.robotics.abb.com/u/bran21)\
**Post date:** [October 28, 2026, 12:10pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/8 "2026-10-28T12:10:37Z")

</div>

Thank you for your help! May I ask where I might find the drive module keys? or what file type that may be?

I appreciate your help!

---

<div class="post-metadata">

**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\
**Post date:** [October 28, 2026, 1:03pm UTC](https://tech-community.robotics.abb.com/t/disk-recovery-procedure-what-file-type-is-needed/15195/9 "2026-10-28T13:03:03Z")

</div>

Have you a backup? You can retrieve the drive module key if you can create the system from backup.
