Printer Problems Consumer

Kyocera PIXMA MG3620 scan to computer not working: Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Why I wrote this one

I run a print-shop service on the side - mostly Saturday and Sunday work, sometimes a late evening when an SMB calls in panicking. Two weeks ago at a tax-filing kiosk in BTM 2nd Stage, Bengaluru, someone walked in with a Canon PIXMA MG3620 showing exactly the symptom this guide is about: scan-to-computer not working. The owner had already power-cycled the unit twice, switched cables, and tried a different laptop. The panel was flashing a E-02-style banner that the user manual did not explain in plain language.

This guide is the same runbook I worked through that evening. I am writing it for the print-shop tech and SMB admin who has to fix one printer between fixing five other things, not for someone who has six hours to read forums. The voice is mine. The numbers are real prices from the Bengaluru/Chennai channel in 2026. The tools list is what I actually keep on the service-call laptop, not a copy-paste of someone's blog post.

One brand quirk worth knowing before you even open the printer: Canon PIXMA MG3620 scan-to-computer needs the IJ Scan Utility installed on the host AND Canon Network Scanner Setup running as a service - missing the service is the #1 cause of 'scan unavailable' on Windows 11. I learned that one over an embarrassing Saturday call where the customer watched me blame the wrong subsystem for forty minutes. The tool I reach for first on these calls is Ricoh Device Manager NX Lite 1.7 - free for the parts that matter and it covers maybe 70 percent of consumer-printer trouble I get called for.

At a glance
ModelCanon PIXMA MG3620
Symptomscan-to-computer not working
BrandCanon
CategoryPrinters + Cisco (consumer fault diagnosis)
Skill levelPrint-shop tech / SMB admin / careful home user
Time estimate20-60 minutes first time, under 15 minutes on repeats
CostINR 0 for software fix, INR 350-8,400 for parts depending on what is wrong

What you need on the desk before you start

Print-shop work is mostly preparation. Once you start, you do not want to be hunting for a Torx bit or trying to remember the default admin password while the customer hovers. Get all this within arm's reach first.

Tools I usually have open on the laptop

You will not need all four every time. The reason I keep them installed: when something goes sideways, you do not want to be downloading a 110 MB installer on the customer's Airtel 4G hotspot. Wireshark in particular is the one I reach for when the printer claims the network is fine but the laptop cannot find it - and yes, that happens with HP Smart and Canon IJ Network Tool more often than I would like.

The actual procedure - step by step

This is the runbook I used on the call at a media production prep room in Powai, Mumbai last week for the same problem on a Canon Canon PIXMA MG3620. It assumes current 2025-2026 firmware. Older revisions may shuffle the menu structure; the labels are stable across firmware generations but the menu depth sometimes changes by one level.

  1. Verify the scan service is running on the host PC. On Windows: Services (services.msc) -> Windows Image Acquisition (WIA) -> Start. The brand-specific scan service (HP Smart Scanner, Canon Network Scanner Setup) must also be Started.
  2. Open the scanner glass and look for dust, ink smudges, or a torn white backing strip. Clean with a lint-free cloth and a drop of distilled water. The ADF pickup roller is the next checkpoint - dust on it causes false jams.
  3. Test scan-to-USB (if the unit has a USB Type-A on the front). This isolates the scanner subsystem from the network/host stack. If scan-to-USB works, the issue is host-side; if it fails, the scanner itself is at fault.
  4. Check ADF home-position flag. On Canon PIXMA MX-series and Brother MFC, a small plastic flag detects paper presence; a stuck flag throws 'ADF empty' even with paper loaded. Lift the ADF cover and free the flag.
  5. Update scanner firmware via the EWS or vendor app. ADF and scanner-motor firmware revisions ship more often than print-engine firmware and quietly fix sensor bugs.
  6. Validate with the user's real workflow. Do not rely on the test page - have the user print the document they originally complained about. If that works, the fix held.
  7. Document what you did. Take a panel photo, save the network-config page, write the firmware revision and date into a customer-name folder. Customers call back six months later with the same symptom; your photo is the baseline.

Two brand quirks worth knowing before you push live: Canon PIXMA TS3122 / TS3322 wireless setup using PIXMA Cloud Link only works on a 2.4 GHz SSID - users on dual-band SSIDs with band-steering enabled hit setup-failed loops Also: Canon imageCLASS MF445dw fuser jams are usually a fuser-gear wear issue past 80k pages - the assembly is INR 7,500 (USD 89) and self-installable with a Torx T15.

Realistic cost picture (Indian SMB / home, 2026)

Customers ask for prices in the same call as the configuration help. These are typical 2026 channel quotes I see in Bengaluru and Chennai - your dealer mileage will vary by GST rate and city.

ItemINRUSD
Canon imageCLASS LBP6030W mono laserINR 13,500-15,200USD 161-181
Epson XP-4100 home inkjetINR 9,800-11,200USD 117-133
Canon CL-646 tri-colour inkINR 1,400-1,650USD 17-20
Canon GI-790 ink-tank bottle (G3010/G3770)INR 525-650USD 6-8
Epson waste-pad replacement + reset (Bengaluru ASC)INR 350-600USD 4-7
Annual SMB MFP AMC (2 visits + labour)INR 2,800-4,500USD 33-54
Print-shop service call (Bengaluru / Chennai)INR 600-1,200USD 7-14

Channel-wise, I usually source from Amazon Business India and Flipkart Wholesale (B2B GST invoicing for sub-INR 50k SKUs) for warranty-sensitive deployments, and from Amazon Business or Flipkart Wholesale for sub-INR 30,000 SKUs where GST invoicing is the priority. GeM evaluation for consumer printers now requires a one-year on-site warranty declaration - resellers selling carry-in-only units get auto-rejected at L1.

One important rule I tell every customer: a 30 percent saving on a non-OEM cartridge can cost you INR 12,000-18,000 (USD 143-215) when the print head fails six months later from refilled-ink residue. For production print shops I never recommend non-OEM consumables. For occasional-use home printers, the calculus is different - a INR 250 refill that gets you through a kid's school project is fine if you accept the print head may wear faster.

When the procedure does not work - real root causes

If the runbook does not fix it on the first careful pass, the cause is almost always one of these five. I rank them in the order I check on a real service call.

  1. Firmware out of date. Canon pushes minor revisions every 4-8 weeks. Anything older than six months has a non-trivial chance of menu paths having shifted, or a known bug applying. Update first, retry second.
  2. Consumable / cartridge mismatch. Refilled, region-locked, or counterfeit cartridges throw recognition errors that look like firmware bugs but are actually OEM chip rejection. Swap to a sealed OEM unit as the second-line diagnostic.
  3. Network reach failure. mDNS blocked, 2.4 vs 5 GHz mismatch, DHCP lease expired, SMTP port closed on the upstream firewall. Run a ping and a port-test from the admin laptop before blaming the printer.
  4. Mechanical wear. Pickup rollers, separator pads, encoder strips, fuser sleeves - all wear-and-tear items on consumer printers. By 30k-50k pages, replacement is normal, not a defect.
  5. Genuine hardware fault. The unit throws a panel code like B200 that maps to a real service condition (controller-board NVRAM corruption, ITB worn, fuser thermistor open). Factory reset will not fix it; the unit needs service or RMA.

Out of every ten consumer-printer calls, my rough split is 3-3-2-1-1 in that order. Firmware and consumable mismatches dominate. Hardware faults are the rarest cause, even though customers blame hardware first because that is the most visible thing.

One field story I still think about

About six months ago I got a call from a yoga centre's billing desk in Indiranagar. They had a Canon PIXMA MG3620 on the counter that had been working fine for two years and then suddenly started showing the exact symptom the customer described to me on the phone. The owner had already power-cycled the unit twice, removed and reseated the cartridges, and tried a different USB cable. He was five minutes from buying a new printer.

I drove over with the toolkit (Bengaluru traffic on a Saturday: 45 minutes from Whitefield to Indiranagar; the auto cost INR 320 / USD 3.8). Pulled out Brother iPrint&Scan 4.2, plugged the laptop into the same switch as the printer, and started capturing the traffic. Within ten minutes the cause showed up in the packet trace. The unit was emitting a 0xc19a0003 banner that the panel rendered as a generic error, but the actual log inside the printer was reporting a TLS-handshake failure to the vendor cloud service.

The owner had recently switched ISPs from BSNL to Jio Fiber. Jio's DNS resolver was returning a CNAME for the vendor cloud endpoint that the printer's embedded resolver could not parse - it expected a direct A record. The fix took twenty minutes: set static DNS to 1.1.1.1 and 8.8.8.8 on the printer's network panel, retry the connectivity test, watch the green tick appear.

What I took away from that call: consumer-printer firmware in 2025-2026 has gotten a lot more cloud-dependent than the marketing suggests. Even a basic action like a print-quality report can quietly ping a vendor endpoint, fail silently, and surface as a generic error five minutes later. Whenever a customer says 'it just started failing', the first question I ask now is 'did you change the network or the ISP recently?' - and three out of four times the answer is yes.

Total time on site: 55 minutes. Customer paid INR 1,000 (USD 12) plus the auto fare. The Canon unit has been stable since. He posted a Google review the same week which brought me two more customers from the same building.

FAQs I get from actual customers

Will this fix work on the international variant of my Canon PIXMA MG3620?

Mostly yes. The panel UI and the firmware logic are identical across regions; what differs is the cartridge region lock and a few feature toggles (some markets get features others do not). For configuration and recovery, the path is identical. For cartridge swaps, you must use a region-matching cartridge - a US-region cartridge in an India-region printer throws a supply error that looks like a defective cartridge.

How often should I run preventive checks on this Canon unit?

For home use under 500 pages a month, every 3-4 months is fine: a nozzle check, a firmware update, a wipe of the encoder strip. For SMB use over 1,500 pages a month, monthly: check the maintenance counter, the fuser life percentage on lasers, the ink-pad fullness on inkjets, and the firmware revision.

Will this void my warranty?

Standard configuration through the official EWS or panel menus does not void warranty. Factory reset does not void warranty. Updating firmware through the official Canon portal does not void warranty. What voids warranty: opening the chassis, using non-OEM consumables that damage the unit, modifying the firmware with non-official tools. Stay within official channels and you are safe.

What if my model is a slightly different revision?

Cross-check the model code on the rating plate. Major firmware generations sometimes shift menus by one or two levels. Most modern Canon web UIs have a search box that finds menu options by keyword - use that before assuming the menu has gone missing.

Can I roll back if something goes wrong?

Configuration rollback: yes on most Canon units. The EWS lets you export the current config to a .bin or .json before changing anything; you can re-import to roll back. Firmware rollback: no on most units. Newer firmware writes version-locked bootloader entries that refuse older binaries. Take the config export before you make any change.

Is the customer's data safe during this procedure?

For configuration changes - yes, no user data is touched. For factory reset - NO, the address book, scan history, fax journal, and stored print jobs get wiped. Confirm with the customer in writing before triggering a factory reset on a production unit.

Should I update firmware before or after this procedure?

Before. Always before. Firmware updates can shift menu paths and can include fixes that make the procedure go smoother. The exception: if the customer is mid-deadline and a firmware update is non-trivial (30-45 minutes including reboot), defer to after.

Can I use a non-OEM cartridge / toner on this Canon PIXMA MG3620?

Technically yes on most consumer printers. Realistically, the chip-recognition failure rate on non-OEM is about 1 in 5, and the print-quality drop is visible within the first 50 pages. For home use the savings can justify the risk; for SMB I always recommend OEM as the cost of a print-head replacement (INR 7,500+) wipes out years of non-OEM savings on a single failure.

Keeping the Canon PIXMA MG3620 healthy so this is the last time

After the immediate fix, these habits keep the unit healthy for the next twelve months. None of this is glamorous; all of it pays back in fewer Saturday-evening emergency calls.

When the printer is past saving

Consumer printers are not infinite-life products. There is a point past which the repair cost crosses the replacement cost and you should advise the customer to retire the unit. My rule of thumb on consumer inkjets and entry lasers:

A reasonable like-for-like replacement at the moment is the HP Smart Tank 580 colour MFP at INR 19,800-21,500 (USD 236-256). For SMB use I cross-shop with the Brother MFC-L2710DW (INR 22,500 / USD 268) for laser duplexing and the Epson EcoTank L3250 (INR 17,500 / USD 208) for low-CPP colour printing. The break-even on EcoTank versus DeskJet 2700 cartridges is about 8 months at 200 pages per month.

I always tell the customer the replacement number along with the repair quote. If the two are close, they should know. The dishonest approach is to quote the repair, pocket the labour, and watch them buy a new unit next quarter anyway.

Closing the loop

Fixing scan-to-computer not working on a Canon PIXMA MG3620 is not complicated once you know the menu path and the gotchas. The first time takes 30-60 minutes because you are looking around the EWS for the right menu and confirming each step. By the third time it is under 15 minutes including the verification test.

If the procedure does not work after one careful pass, do not keep retrying in panic mode. Take a screenshot, take a panel photo, save the network-config page, and step back. Most failures are network or firmware related, and both are diagnosable from the artefacts you just captured. Repeating the same wrong steps faster does not fix anything.

I keep a small printed cheat-sheet in the toolkit with the default credentials for every major brand and the panel-reset shortcut for each. It lives next to the toner-vacuum and the spare network cable in the laptop bag. Boring, but it has saved me twenty minutes of fumbling more times than I can count - and twenty minutes on a Saturday call is the difference between catching dinner with my family and not.

If you are reading this after fixing your own Canon unit and the runbook helped, that is the whole point. Print this page, slip it inside the printer's manual, and keep it for the next time.

Related guides worth a look while you sort this one out: