Operational playbooks
IrfanView guides for reliable Windows deployments
Each section is written as a sequence you can hand to help desk staff. Where risk is involved, especially batch deletes or format conversions, the steps bias toward backups first and proof before destructive actions.
Browse guides
Jump to a playbook below. Cards link to the full step-by-step section on this page.
Metadata looks wrong after export
Compare dimensions, DPI, and color depth between source and export one change at a time.
Open guide →Thumbnails crawl on network shares
Isolate storage latency, tune thumbnail size, and pause sync clients during browsing.
Open guide →TWAIN acquisition fails or freezes
Refresh vendor drivers, release exclusive TWAIN sources, and log versions for handoff.
Open guide →Batch jobs hang mid queue
Split large files, disable filters, and watch disk saturation beyond CPU alone.
Open guide →Plugin install order and cleanup
Close the app, upgrade base first, remove duplicate plugins, then smoke test formats.
Open guide →Batch best practices for production folders
Pilot small sets, keep manifests, and never delete originals before spot checks.
Open guide →Windows Defender or endpoint quarantine loops
Capture detection names, compare hashes to golden records, and escalate with evidence.
Open guide →Antivirus warnings without obvious malware behavior
Structural detections may still need formal exceptions when hashes and behavior look normal.
Open guide →Full playbooks
Metadata looks wrong after export
- Open the information dialog on the source file and write down dimensions, DPI, and color depth.
- Export with one obvious change only, for example resize without simultaneous format change.
- Open the exported file and compare fields line by line.
- If DPI shifts, inspect whether the export dialog reset DPI to screen defaults.
- If color shifts, test without color management plugins and retest with a minimal plugin set.
Related: Feature hub for inspection
Thumbnails crawl on network shares
- Confirm whether the share is high latency or saturated by other jobs.
- Test the same folder on a local SSD to isolate storage from IrfanView.
- Temporarily reduce thumbnail size in settings to lower decode cost.
- Pause sync clients that scan every touched file during browsing.
- Document the outcome so network owners get a reproducible path.
Related: Catalog workflows
TWAIN acquisition fails or freezes
- Update the scanner vendor bundle from the manufacturer, not a random mirror.
- Close other apps that might hold the TWAIN source exclusively.
- Try a lower preview resolution to reduce USB bandwidth spikes.
- Create a new Windows profile test only if policy allows, to rule out user hive corruption.
- Log the exact driver version in your ticket for the next engineer.
Related: Device capture overview
Batch jobs hang mid queue
- Sort inputs by size and retry only the largest files alone.
- Disable optional filters to see whether a specific transform triggers the stall.
- Watch Task Manager disk and GPU columns for saturation, not only CPU.
- Copy a failing file locally before retrying to remove network variables.
- If one corrupt file blocks a queue, split batches by subdirectory.
Related: Batch feature section
Plugin install order and cleanup
- Close IrfanView completely before changing plugins.
- Install or upgrade the base application first, plugins second.
- Remove obsolete plugin duplicates rather than stacking versions.
- Restart once, then open a small test image per new format family.
- Record the final plugin directory listing in your change record.
Related: Plugin architecture
Batch best practices for production folders
- Copy sources to a scratch volume when millions of files are involved.
- Run a pilot on ten files, then a hundred, then the full tree.
- Never delete originals until a second tool spot checks random outputs.
- Keep a manifest of paths touched for rollback discussions.
- Document which operator account ran the job for audit trails.
Windows Defender or endpoint quarantine loops
- Identify whether the block happens at download time or execution time.
- Capture the detection name exactly as shown in the console.
- Compare file hash to your internal golden record for that release.
- If hashes match the approved package, escalate to security with that evidence.
- If hashes differ, discard the file and republish from a known clean channel.
Also read: Download page antivirus context and FAQ deep dive
Antivirus warnings without obvious malware behavior
Some detections are structural, not behavioral. When the program launches, behaves normally, and hashes match a trusted record, your security team may still require a formal exception. Provide installers, hashes, release notes, and a short video of expected UI behavior to speed approval.
Trust statement