While install mode is Cisco's recommended approach for IOS-XE switches, there are valid scenarios where you may need to revert to bundle mode — for example, when downgrading to an older IOS version that does not support install mode, recovering a switch using a legacy image, or troubleshooting install mode corruption. This guide covers the correct procedure to safely convert Cisco switches from install mode back to bundle mode, with instructions applicable to the Catalyst 9200, 9300, 9400, 9500, 3750, and 3560 series.
The procedure described in this guide applies to the following Cisco switch families, with platform-specific notes where applicable:
Note: The Catalyst 9000 series runs IOS-XE and uses the install command framework. The 3750 and 3560 series run classic IOS and do not use the install framework — their conversion process is simpler and is covered in the dedicated section at the bottom of this guide.
Converting back to bundle mode is generally not recommended for production environments, but may be necessary in these situations:
packages.conf is corrupted and cannot be rebuiltBefore starting, ensure the following are in place:
.bin monolithic bundle file compatible with your switch model1. Confirm the switch is currently running in install mode:
show version | include mode show install summary show boot
You should see output indicating Install mode and packages.conf as the boot variable.
2. Document the current system state:
show version show install summary dir flash:
3. Back up the current running configuration:
copy running-config startup-config copy startup-config tftp://192.168.10.10/switch-backup-before-revert.txt
4. Check available flash storage:
show flash: | include bytes
If the monolithic bundle .bin file is not already on flash, copy it from your TFTP server or USB drive.
Via TFTP:
copy tftp://192.168.10.10/cat9k_iosxe.17.06.05.SPA.bin flash:
Via USB:
copy usbflash0:cat9k_iosxe.17.06.05.SPA.bin flash:
Replace the filename with the appropriate bundle image for your platform and target version.
Confirm the file is present in flash and verify its MD5 checksum against the value from Cisco's software download page.
dir flash: | include cat9k_iosxe.17.06.05.SPA.bin verify /md5 flash:cat9k_iosxe.17.06.05.SPA.bin <expected-md5-hash>
Enter global configuration mode and remove the existing packages.conf boot entry.
configure terminal no boot system flash:packages.conf
If there are multiple boot system entries, remove each one individually:
show running-config | include boot system
no boot system flash:packages.conf no boot system flash:<any-other-entry>
Configure the switch to boot directly from the monolithic .bin bundle file.
boot system flash:cat9k_iosxe.17.06.05.SPA.bin exit
Save the running configuration so the new boot variable persists after reload.
copy running-config startup-config
Verify the boot variable is correctly set:
show boot
Confirm the output shows your .bin file as the boot system — not packages.conf.
Before reloading, remove the installed packages to free up flash space. This step is optional but prevents confusion from leftover install mode files.
Remove all inactive packages:
install remove inactive
To remove all install mode packages (active and inactive) — only do this after confirming your bundle image is on flash and boot variable is correctly set:
install remove all
Warning: Do not run install remove all if your switch is still configured to boot from packages.conf, as this will leave the switch with no bootable image.
Reload the switch to boot into bundle mode.
reload
When prompted to save configuration, enter no (you already saved in Step 5).
After the switch comes back online, confirm it is running in bundle mode.
Check boot mode:
show version | include mode
Verify boot variables:
show boot
Confirm no install packages are active:
show install summary
Success Indicators:
show boot shows the .bin file (not packages.conf)show install summary shows no active packages or is emptyThe Catalyst 3750 and 3560 series run classic IOS — not IOS-XE — and do not use the install mode framework at all. These switches always boot from a single monolithic .bin image. There are no packages, no packages.conf, and no install commands.
If your 3750 or 3560 is booting from an incorrect or corrupted image, or you need to change the active IOS image, follow these steps.
copy tftp://192.168.10.10/c3750e-universalk9-mz.152-4.E10.bin flash:
dir flash: | include .bin verify /md5 flash:c3750e-universalk9-mz.152-4.E10.bin <expected-md5-hash>
configure terminal no boot system flash:<old-image.bin> boot system flash:c3750e-universalk9-mz.152-4.E10.bin exit
copy running-config startup-config show boot reload
show version show boot
On 3750/3560 switches, show version will confirm the currently running IOS image filename. There is no mode indicator, as these switches only support bundle-style (single binary) boot.
Note for Stacked 3750 Systems: In a stack, all member switches must have the same IOS image in flash. Verify all stack members before reloading:
show switch detail dir flash: (on each stack member via session)
1. Verify system version and boot mode:
show version show boot
2. Check network connectivity and interface status:
ping <gateway-ip> show ip interface brief
3. Verify Layer 2 features and VLANs:
show interface status show vlan brief show spanning-tree summary
Review CPU, memory, and system logs after the revert:
show processes cpu | include five show memory statistics show logging | include ERROR|WARN
After confirming stable operation in bundle mode, clean up residual install mode files to reclaim flash space.
List all files in flash:
dir flash:
Delete individual package files (they typically have a .pkg extension):
delete flash:<package-file.pkg>
Delete the packages.conf file if it still exists:
delete flash:packages.conf
Delete any stale .conf or .tmp install artifacts:
delete flash:*.conf delete flash:*.tmp
Verify reclaimed space:
show flash: | include bytes
Caution: Do not delete the startup-config or any image you intend to keep as a backup.
This usually means the boot variable was not saved, or packages.conf still exists and is taking precedence. Verify:
show boot show running-config | include boot system
If packages.conf is still listed, reenter configuration mode and correct it:
configure terminal no boot system flash:packages.conf boot system flash:<your-bundle.bin> exit copy running-config startup-config reload
If the switch cannot find or load the bundle image, access ROMMON and boot manually:
SWITCH_NUMBER=1 BOOT=flash:cat9k_iosxe.17.06.05.SPA.bin boot
Once the switch boots, reconfigure the boot variable and save.
Bundle images are large. Free space by removing install packages and unnecessary files before copying:
install remove inactive delete flash:*.log delete flash:*.tmp show flash: | include bytes
Do not proceed if the MD5 checksum does not match. Re-download the image from Cisco's software portal and retransfer it:
delete flash:<corrupt-image.bin> copy tftp://192.168.10.10/<image.bin> flash:
If the switch fails to boot after the conversion attempt, use ROMMON to boot directly from a known-good image.
SWITCH_NUMBER=1 BOOT=flash:<known-good-bundle.bin> boot
After booting, reconfigure and save the boot variable permanently:
configure terminal no boot system flash:packages.conf boot system flash:<known-good-bundle.bin> exit copy running-config startup-config
If bundle mode causes issues and you want to return to install mode, copy a compatible image and re-run the install process:
configure terminal no boot system flash:<bundle.bin> boot system flash:packages.conf exit copy running-config startup-config install add file flash:<image.bin> activate commit
While bundle mode works reliably, be aware of its limitations compared to install mode:
.bin files are significantly larger than extracted packagesFor these reasons, Cisco recommends reverting to bundle mode only when necessary and planning a return to install mode once the underlying issue is resolved.
# 1. Copy bundle image copy tftp://<server>/<image.bin> flash: # 2. Remove install mode boot variable configure terminal no boot system flash:packages.conf # 3. Set bundle boot variable boot system flash:<image.bin> exit # 4. Save and reload copy running-config startup-config reload # 5. Verify show version | include mode show boot
# 1. Copy new IOS image copy tftp://<server>/<image.bin> flash: # 2. Update boot variable configure terminal no boot system flash:<old-image.bin> boot system flash:<new-image.bin> exit # 3. Save and reload copy running-config startup-config reload # 4. Verify show version show boot
Converting a Cisco switch from install mode back to bundle mode is a straightforward process when followed in the correct sequence: transfer and verify the bundle image, remove the install mode boot variable, set the new bundle boot variable, save configuration, and reload. The same logical process applies across the Catalyst 9200, 9300, 9400, and 9500 series running IOS-XE.
For the Catalyst 3750 and 3560 series running classic IOS, the concept is even simpler since these platforms have always used a single monolithic boot image — the process is simply a matter of updating the boot system variable to point to the desired image.
Remember that bundle mode is a legacy boot method for IOS-XE platforms, and a return to install mode should be planned once the need for bundle mode has passed. Proper planning, console access, and image verification are the keys to a smooth and safe conversion in either direction.