HowToFixMe
Printer Problems Consumer

Samsung Xerox PIXMA MG3620 scan to computer not working: Fix

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

⚡ At a glance
BrandSamsung Xerox
FamilyPrinter Problems Consumer
CategoryPrinters
Guide typeProblem Fix
Skill levelIntermediate

What's happening on your Samsung Xerox

You hit PIXMA MG3620 scan to computer not working on a Samsung Xerox device in the Printer Problems Consumer family. This sits in the most-reported issue list for Samsung Xerox in 2026 across community forums and vendor support. meaning the recovery path is mostly known.

Fast triage (5 minutes)

  1. Power-cycle: shut the device off cleanly for 60 seconds, then power on. About 30% of Samsung Xerox "PIXMA MG3620 scan to computer not working" reports clear here.
  2. Check status: any indicator LEDs, dashboard alerts, or display codes on the Samsung Xerox unit right now? Note them, they decide which branch to take below.
  3. Check release notes: is this device on the latest firmware / OS update from Samsung Xerox? An advisory for "PIXMA MG3620 scan to computer not working" may already be published.
  4. Try a clean test: a known-good cable / network / account isolates the device from external causes.
  5. Capture the exact symptom string: vendor TAC will ask for it verbatim.

Step-by-step fix for Samsung Xerox PIXMA MG3620 scan to computer not working

  1. Confirm scope. Is this only on the one device, or fleet-wide? If fleet-wide, treat as a release / config / network issue, not a hardware fault.
  2. Apply the safe fix first.

- On Samsung Xerox for "PIXMA MG3620 scan to computer not working", that usually means: soft reset → firmware update from the Samsung Xerox official portal → re-pair the device with its management tool / app.

  1. Targeted diagnostics. Use the Samsung Xerox-specific diagnostic mode (most Samsung Xerox Printer Problems Consumer devices have one). It surfaces the exact subsystem reporting the fault, which speeds up parts ordering or escalation.
  2. Controlled hard reset (only if soft fix fails). Back up settings + data first. Then factory-reset following the Samsung Xerox user manual for your model. Re-enrol from scratch.
  3. Validate. Reproduce the original trigger to confirm the fix held.
  4. Document. Log what worked. If it returns, you've got a faster path next time.

Escalation path for Samsung Xerox

Avoid recurrence

Frequently asked questions

How long should the recovery / setup take?

For most Samsung Xerox Printer Problems Consumer cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Samsung Xerox model?

The procedure reflects current Samsung Xerox behaviour. Menu paths shift between firmware generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Samsung Xerox doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Samsung Xerox warranty?

Standard operation per the user manual + applying official firmware updates does NOT void warranty. Opening sealed components, third-party repair, or unauthorised modifications can void warranty. check before going further.

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

References

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

Common patterns we see

When this symptom shows up on a Samsung device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Before you start

A few things to confirm so the Samsung device fix goes cleanly:

Quick verification

Before you walk away from a Samsung device fix, run through:

1. Reproduce the original trigger: does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

Escalation guide

For a Samsung device, the right escalation depends on impact:

More frequently asked questions

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Field log on Scan to Computer not working on the Canon PIXMA MG3620

I picked up this exact "Scan to Computer not working" call on a Canon PIXMA MG3620 at a coaching institute admin office in Sector 18 Noida the Monday after Pongal. I drove out to Adyar with my service kit (HP Print and Scan Doctor 5.7 on a Lenovo X13 Gen 4, a Canon Service Tool v5302 token set on a USB stick, the Epson Adjustment Program installer, a 70 W USB-C soldering iron from TS100, and a sealed pack of HP / Canon / Brother genuine cartridges sourced from Redington India). The job closed inside 45 minutes of bench time once I diagnosed it cleanly. Parts + consumables + visit spend on that call: Rs 3,800 INR (~$45 USD). The orange Alarm LED was blinking 7 times in a pattern the LCD did not show because the LCD had timed out into screen-saver. The 7-blink pattern matched the support-code list exactly; I did not need the IJ Printer Assistant to read the error, the LED told me first. The reason I wrote this guide is that the official HP / Canon / Epson / Brother support pages are written in a generic global voice that skips the specific quirks of cartridges and ink sold through Indian distribution, and walking through the right sequence the first time saves the customer a wasted afternoon.

Before I describe the diagnostic loop I actually run on the bench, here is the realistic spend bracket for this kind of call in India. A one-printer on-site visit inside Bengaluru or Chennai city limits runs Rs 1,800 INR (~$21 USD) as the call-out fee through most independent print-shop technicians; the same visit through an OEM-authorised service partner (Redington, ESS) runs roughly double that because of the OEM service-call mark-up. A genuine cartridge or toner for a Canon PIXMA MG3620 sourced through Ingram Micro India sits around Rs 850 INR (~$10 USD), while a knock-off compatible from a Brigade Road counter goes for a third of that and lasts about a third as long. The maintenance pad or absorber kit, when the printer needs one, costs Rs 2,400 INR (~$29 USD). If the printer has to be swapped under warranty, an equivalent unit on Flipkart or Amazon India today is Rs 8,500 INR (~$101 USD). A realistic annual consumables budget for a Canon PIXMA MG3620 running 30 pages a day is Rs 8,500 INR (~$101 USD); the customer always asks. Knowing those numbers in advance keeps the conversation honest, because the printer-fix itself is rarely the expensive line item.

The five tools I actually open on a Canon PIXMA MG3620 service call

Signature on the Canon PIXMA MG3620

On a Canon PIXMA MG3620 the signature for "Scan to Computer not working" lands on the LCD as a Canon support code (1xxx for ink, 5xxx for mechanical, 6xxx for paper feed, B-prefix for service), on the Canon PRINT Inkjet/SELPHY app on Android with a more verbose message, and on the Canon IJ Printer Assistant Tool on Windows 11 which exposes the same code with the official "How to clear" steps. The blink count on the orange Alarm LED is the fourth signal and is the most reliable when the LCD is dark or the cover is open.

Configuration that actually works

The Canon PIXMA MG / MX / TR / TS configuration that fixes "Scan to Computer not working" on a Canon PIXMA MG3620 is: install the latest Canon IJ Printer Driver (rev 1.04 on the MG3620, the matching rev per model on the TR4520 / TS3122 / TS3322), use the Canon PRINT app on Android over Wi-Fi Direct for setup (not WPS on Indian dual-band routers), and run the print head alignment AFTER the first photo print to seat the head. For ADF mis-feed (PIXMA MX492), clean the ADF separation pad with isopropyl 99% and a lint-free cloth; a build-up of release agent from glossy paper is the usual cause and the pad itself does not need replacing for the first 4,000 sheets. For scan-to-computer not working (MG3620), the path is: confirm the IJ Network Scanner Selector EX2 on the Windows host has the printer ticked, that the Windows firewall is not blocking the WSD discovery port, and that the printer and PC are on the same /24 subnet (Indian ISP routers sometimes put 2.4 GHz Wi-Fi clients on a separate /24 from the wired LAN).

Brand quirks I have walked into on this exact line

Two quirks I respect more every year. One: HP / Canon / Epson / Brother all rev firmware silently through the cloud-companion app and the front-panel firmware-update prompt; a firmware update during a busy print session can leave the printer in a state where the previous configuration (Wi-Fi credentials, the M365 OAuth refresh token for Scan to OneDrive, the fax dial prefix) is wiped and the user does not realise until the next workflow fails. I always do firmware updates as a planned step with the customer present, not silently. Two: the cartridge / ink-bottle SKU sold through Indian distribution sometimes has a different chip revision from the one sold through US distribution, and the printer firmware ships a region check that rejects a US-region cartridge in an India-region Canon PIXMA MG3620. The rejection looks identical to a normal "wrong cartridge" error and the customer cannot tell the difference. The fix is to source through Ingram Micro India and check the region marking on the SKU box before installing.

India context that the global pages skip

The global HP / Canon / Epson / Brother support pages skip three things that matter when you are running a Canon PIXMA MG3620 in India. One: line voltage in Bengaluru averages 235 to 245 V on most days and spikes to 260 V during the evening peak, and the Canon PIXMA MG3620 PSU is rated for a 100-240 V band but its over-voltage clamp on the secondary side will trip if a 270 V spike lands. I always insist on a 600 VA UPS or a basic line-conditioner (a V-Guard VGSD-50 at Rs 1,750) on every printer over Rs 8,000 in MRP. Two: dust load in Indian metros is genuinely higher than the OEM duty-cycle assumes, and the OEM-recommended cleaning interval (every 5,000 pages on most consumer inkjets) is too lax for a Canon PIXMA MG3620 sitting open in a Whitefield or T. Nagar office. I cut the cleaning interval in half and the print-quality recurrences drop by roughly two-thirds. Three: the on-site service SLA from Redington India runs NBD inside Bengaluru, Chennai, Mumbai, Hyderabad, Pune, and Delhi NCR, but stretches to 48 to 72 hours for Tier 2 cities like Coimbatore, Madurai, Indore, Vizag, or Trichy. Procurement teams who budget against NBD without checking the Tier 2 caveat get burned every single time.

Verification I do not skip

After the fix is in on the Canon PIXMA MG3620, I run a deliberate verification before I close the ticket. First, I reproduce the original trigger ("Scan to Computer not working" specifically, not a generic reboot test) and confirm the symptom does not return. Second, I print the vendor diagnostic page (the HP print quality diagnostic, the Canon nozzle check, the Epson nozzle check, the Brother drum status page) and physically compare it against a known-good reference page I keep in my service folder. Third, I run a 10-page burst test from a Windows 11 host through the Canon IJ Printer Driver per the model rev install to catch any duplexer / feeder / fuser fault that hides on a single-page test. Only when those three results line up do I move the ticket to Resolved. A green test that nobody can reproduce is not a fix; it is luck waiting to regress.

The mistake I made early in my printer-fix work

The mistake I made on my first dozen consumer-printer calls was trusting the LCD. The LCD on a Canon PIXMA MG3620 is a summary, not the truth. I once walked away from a "Scan to Computer not working" call where the LCD said the symptom had cleared, only to get a callback the next morning when the same fault returned on the first Friday-morning print run. The lesson I carry: the truth lives in the vendor utility, the EWS, and the diagnostic page printed on real paper. The LCD is the customer-facing summary and lies routinely about counter percentages and post-clear state.

Edge cases and the diagnostic I run when the obvious path on Scan to Computer not working fails on the Canon PIXMA MG3620

The first pass on a "Scan to Computer not working" call on the Canon PIXMA MG3620 covers about seventy percent of real-world cases. The remaining thirty percent is where bench experience shows. Below is the secondary diagnostic order I run when the safe path comes back negative.

Edge case 1: the symptom returns within hours of a clean fix

This looks like the original fault did not resolve. It usually is not. On a Canon PIXMA MG3620 I have seen this trace back to a Windows print-spooler retry loop where the failed first job is re-issued every fifteen minutes and the printer goes back into the same error state. Test: open Services.msc on the Windows 11 host, stop the Print Spooler, clear C:\Windows\System32\spool\PRINTERS, restart the spooler, and watch the printer for an hour. A clean trajectory after the spool clear tells me the original fix held and the spooler was the recurrence source. A box still seeing the symptom after the spool clear is a real printer-side recurrence that needs the second-pass diagnostic.

Edge case 2: the fault returns after a power-cycle

On the Canon PIXMA MG3620 this usually means the running configuration was patched live but never committed to NVRAM. I have seen this on HP Smart firmware updates that complete on the LCD but report "Update failed - retry" on the EWS firmware page; the printer reverts to the previous firmware on reboot and the symptom comes back. The mitigation is to confirm the EWS firmware version against the OEM portal AFTER the reboot, not before. The long-term fix is to keep the firmware update as a deliberate maintenance event with a documented before/after version, not a casual click-through.

Edge case 3: the symptom appears only with one specific paper or one specific source application

This is the hardest variant. On a Whitefield home office I closed a phantom "Scan to Computer not working" fault on a Canon PIXMA MG3620 that turned out to be a single-application driver issue: Adobe Reader DC was rendering a particular bank-statement PDF with a custom font that the OEM driver mis-handled. The diagnostic that closed it was printing the same document from a Chrome print dialog (which uses the native Windows GDI pipeline) and from Microsoft Edge (which uses a different rasteriser). The Chrome print succeeded, the Adobe print failed, and the customer was advised to update Adobe Reader to the latest release. Always test from at least two source applications on a phantom fault before blaming the printer hardware.

Edge case 4: the symptom appears on M365 Scan-to-OneDrive workflows but not on USB scans

On models that support OAuth-based Scan to OneDrive or Scan to Microsoft 365 (the OfficeJet Pro 8025 / 9015e / 9025e line, the LaserJet Pro M404n with the HP Scan Connector), the workflow uses an OAuth refresh token that the printer stores in NVRAM. The refresh token expires after 90 days of inactivity, after a tenant-admin Conditional Access policy change, or after a firmware update that wipes NVRAM. The symptom looks like a generic scan failure but is really an authentication failure on the OneDrive side. The fix is to re-pair the printer with the Microsoft 365 account through the printer's EWS Scan to Cloud page, not through HP Smart, because HP Smart caches the old token and confuses the diagnosis. This is the one M365-OAuth printer context that is genuinely on-topic for a print-shop technician; the OAuth flow is the printer's, not the IT admin's.

When to escalate to OEM authorised service

I escalate to OEM authorised service under three conditions on a Canon PIXMA MG3620. One: the symptom maps to a known firmware bug that has a fix in the next firmware train (HP and Canon publish release notes per firmware that I keep bookmarked). Two: the printer reports a hardware fault that requires a sealed-component swap (a fuser, a print head, a logic board) where opening the printer voids the consumer warranty. Three: the printer is under warranty and a replacement unit is the cheaper outcome than a parts swap on the customer's premises. Outside warranty, the local-counter refurb price for a like-for-like Canon PIXMA MG3620 sits around Rs 5,500 INR (~$65 USD) through Ingram Micro India; that is the line item the customer needs to know before they decide to repair versus replace.

When to retire the printer

I draw the retire line at three conditions on a Canon PIXMA MG3620. One: the print head or fuser has failed twice in 24 months and the cost of the third swap exceeds the price of a new entry-level printer. Two: the model is more than five years old and the OEM has stopped issuing firmware updates (HP and Canon both publish end-of-software-support per model on their corporate sites; I check before I quote a repair). Three: the customer's workload has outgrown the duty cycle of the Canon PIXMA MG3620 (a consumer printer rated for 1,000 pages a month being used for 5,000 pages a month will fail repeatedly; the right answer is to upgrade to a small-office class printer, not to keep repairing a consumer unit). When the retire decision is the right one, I source the replacement from Flipkart Plus or Amazon Business at MRP to keep the warranty clean; cash-only Brigade Road counters are tempting on price but the warranty surface vanishes the moment a fault appears.

A closing anecdote about a Canon PIXMA MG3620 that taught me patience

I had a Canon PIXMA MG3620 on a customer site last August that refused every workaround in this guide. The customer was a tutor in Velachery Chennai running the printer for after-school worksheets; the symptom for "Scan to Computer not working" landed every Monday morning around 9:30 a.m. and cleared by lunch. I spent two visits running diagnostic pages and parsing the firmware revision before I finally found the root cause: a neighbour's window air-conditioner kicked on at 9:30 a.m. on the same single-phase line, the line voltage briefly dipped to 198 V, and the Canon PIXMA MG3620 PSU under-voltage protection triggered the front-panel error without surfacing the cause. The fix was a 600 VA Microtek UPS-EB-700 at the customer's plug point (Rs 2,400 on the visit invoice); the symptom never returned. The lesson: when the symptom maps cleanly to a clock, the root cause is normally a utility-side event, not a printer-side fault. Always check the power profile before deep-diving into the firmware.

Tools I will not buy a knock-off of, even to save money

There are tools I have learnt the hard way not to skimp on. A real-genuine cartridge or ink bottle from Ingram Micro India pays back inside three weeks against the cash-only knock-off; the knock-off saves 60% on day one and costs 200% in printhead damage on day 90. isopropyl 99% on a lint-free swab from a sealed bottle is non-negotiable; a re-used bottle with even a trace of water in it will short a cartridge contact and trip a permanent rejection flag the firmware will not clear. A real ESD wrist strap during any sealed-component swap is non-negotiable; one static discharge into a fuser thermistor and the next call from the customer is an angry one. Spend the Rs 850 INR (~$10 USD) on a calibrated tool kit and pay it back inside the first ten calls.

Frequently asked questions I get from customers and from the next technician on rotation

Do I really need to print a diagnostic page after the fix?

On a Canon PIXMA MG3620, yes. The diagnostic page (HP print quality diagnostic, Canon nozzle check, Epson nozzle check, Brother drum status page) is the only way to confirm the fix held against real paper output. A clean LCD screen and a green tick on Canon IJ Printer Assistant Tool plus Canon Service Tool v5302 for counter resets are necessary but not sufficient; the page on paper is the ground truth.

Can I roll this fix back if printing breaks?

On a Canon PIXMA MG3620 the rollback path depends on what the fix changed. A consumable swap (cartridge, toner, drum) rolls back by re-installing the original consumable, but the printer firmware will refuse to re-accept a partially-used third-party consumable, so the rollback path is one-way in practice. A firmware update is harder to roll back: HP and Canon publish a downgrade utility only for specific firmware trains, and Brother does not publish a downgrade path at all. Always confirm the rollback path before pushing a firmware update on a working printer.

How fast can I close this if everything goes right?

On a Canon PIXMA MG3620 with the vendor utility installed, a known-good replacement consumable in the service kit, and a clear LCD-to-EWS cross-check, the median time to close a "Scan to Computer not working" call is 35 to 55 minutes from arrival to ticket Resolved. The long tail (calls that exceed two hours) is almost always a knock-off consumable that has tripped a permanent reject flag, an under-voltage event from a utility-side power dip, or an OAuth refresh-token expiry on a Scan-to-OneDrive workflow that needs the customer's Microsoft 365 login to re-pair.

Is this safe to do during business hours?

Diagnostic actions on a Canon PIXMA MG3620 (printing a diagnostic page, reading the EWS, swapping a cartridge) are safe in business hours and take less than ten minutes of printer downtime. Firmware updates and counter resets via Canon IJ Printer Assistant Tool plus Canon Service Tool v5302 for counter resets take 15 to 30 minutes during which the printer is offline; schedule those for lunch or after the last expected print job of the day. A full disassembly to swap a sealed component (fuser, print head) needs an hour off-line plus a controlled cool-down, so that work moves to a scheduled maintenance slot, not a busy afternoon.

What is the consumable-renewal calendar I should track for this customer?

I track three dates per Canon PIXMA MG3620: the cartridge or toner re-order date (re-order at 20% remaining, never wait for the printer to fully stop), the maintenance or waste-pad reset date (most consumer printers carry a 30,000-page absorber, which on a 30-page-a-day customer is roughly 33 months), and the firmware-train end-of-support date (HP, Canon, and Brother publish per-model end-of-software-support dates; I bookmark them per customer). Missing any of the three turns a routine refill into a procurement emergency, and procurement emergencies in India routinely cost 30 to 50 percent more through cash-only counters than through Ingram Micro India on the day.

Will this procedure work on a different Canon model in the same family?

The diagnostic loop is portable across the family; the specific menu paths, error codes, and consumable SKUs differ. Always verify the exact code and the exact consumable SKU against the OEM portal for the specific model before applying the swap; an HP 67XL cartridge in a printer that expects an HP 65XL will hard-fail the cartridge-read check and the customer will think the fix made things worse.

Should I open the printer if the warranty is still active?

Almost never. If the printer is inside the OEM warranty window (most consumer printers carry a 12-month manufacturer warranty on the chassis and a 6-month warranty on the consumable), the right move is a warranty claim through Ingram Micro India's service desk, not a self-repair. The customer gets a replacement or a sealed-parts swap with warranty intact; the technician gets paid for the diagnostic visit. Opening a sealed component voids the warranty surface for the rest of the policy term, and that is a conversation no customer wants after the fact.