Device isn’t quite ready for Windows 10 update

Situation: The client’s computer shows this message: The Windows 10 May 2019 Update is on its way. We’re offering this update to compatible devices, but your device isn’t quite ready for it. Once your device is ready, you’ll see the update available on this page. There’s nothing you need to do at this time.

Resolution: Since some of new feature are not compatible with certain hardware, drivers or installed software in your computer, the update will not be installed . If you try to download and install the feature update, it may cause booting problems, BSOD, crashes or performance issues after upgrade. The best solution of this problem is wait for some time until Microsoft fixes the incompatibility issue between your computer hardware and Windows 10 feature update.

“Save Print Output As” in a folder

Q: Hi Bob. Our reception 2 computer went through an update last night. Now, when we go to print from DVMAX, it automatically is going to “Save Print Output As” in a folder, instead of printing right away. Any ideas on how to fix this?

A: Open the Properties of the printer. Click on Ports. File: Print to file is checked. Check the printer instead that should fix the problem.

Can’t print to a shared label printer in DVMax

Situation: The client can’t print to the shared label printer in DVMax after they install the printer.

Troubleshooting: 1. Make sure the label printer is shared on DVMax by following this post:

How to configure Label printer on in DVMAX

2. If the shared printer is configured correct on DVMax, on the client side, make sure “This station prints labels” is checked. Also make sure you have * on the shared label printer if you have multiple label printers.

3. Make sure the shared printer name is correct. In above example, the first printer name should be Pharmacy1 instead of Pharmacy Label Printer.

4. Make sure the correct port is selected, for example \\pharmacy2\dymo LabelWriter.

5. If you don’t see the Printer driver, it may be you haven’t install the shared printer locally. Add the shared printer on the client computer.

6. The Label Printer type should be Driver-Based Printing instead of DYMO Label Printer as shown above.

7. Make sure the shared printer is update the list on the host computer and make sure the printer is shared.

8. If the host has shared the printer and you can see it on DVMax, you need to go to File>Label Printer Setup>Setup to make changes such as Label printer type, Selected Printer Driver and Label Printer Name. You also have a option to test the print.

Can’t print to label printer on DVMax

Whenever you change a computer name, username or have a Windows update, DVMax may have problem to send a print job to Label printer .

Here are some troubleshooting: tips:

  1. If there is a Windows update hosting to restart, go head to do so.
  2. If the shared printer is offline or out paper (that is not true and you have paper in the printer), restart the computer or reset the printer.
  3. To reset the printer, please unplug the USB/Printer cable and unplug power cable.
  4. Reset the Label printer by following steps: 1) Close all open client, patient, invoices, appts, etc. until you’re looking at the main screen of DVMAX.
    2) Go to the File menu and choose Setup Label Printers.
    This Station has an attached Label Printer should be checked.
    If this station should be Shared with other stations, verify that Setting is checked also.
    3) Click on the Setup tab.
    Label Printer Type should be: Dymo/CoStar Label Writer if it is connect to Com#. Otherwise, select Shared Printer.
    4) Label Printer Port be set to the port your Label printer is on. Typically this is KeySerial1 on a Macintosh. For Windows, it can be anywhere from COM1 – COM8, or sharedPrinter name.
    5) Click Print Test Label once you have chosen a port/printer to use and give it 5-10 seconds to see if the Labeler responds.

Only one copy was printing while more than one copy required

Situation: The client has a problem to print multiple copies. When he tries, he get this message: Only one copy was printing while more than one copy required. RAM disk is full or not enabled. Or, SSD or SD Card is full.

Troubleshooting: If it is HP printer, try to disabling Mopier mode.

  1. Start > Devices and Printers
  2. Double-click printer
  3. Double-click “Customize your printer”
  4. Click “Device Settings” tab
  5. Scroll to bottom of page and change “Mopier Mode” to Disabled under the “Installable Options” group.

If it is Kyocera printer, you may try to install Printer RAM Disk.

Note: 1. If this printer is in server, please enable Printer RAM Disk.

2. You may need to restart Pinter spooler on both server and client.

Windows Update causes network problem

Situation: Whenever the client installs Windows update, it causes network traffic problem and makes internet slow.

Troubleshooting: We recommend to setup WSUS server to download the updates and distribute them to all computers .

Also, Microsoft recommend this:

The following group policies can help mitigate this:

Other components that reach out to the internet:

Many Windows and update problems can be fixed by running SFC and DISM

If you experience a Windows problem or Windows update problem, you may try to run System file check (SFC) and to fix it.

To run a system file check (SFC)

Go to start>Type CMD

Right click and run as Administrator

Type sfc /scannow

It may shows one of three possible results:
Windows did not find any integrity violations (a good thing)

Windows Resource Protection found corrupt files and repaired them (a good thing)

Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)  If you get this message run DISM as described below

To RESTORE health (recommended)

Use DISM /Online /Cleanup-Image /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file.  This generally takes 15-30 minutes depending on the corruption and size of the partition.

Note: 1. You may have to run this up to 3 times to fix all the problems.

2. After running DISM it is a good idea to re-run SFC /scannow to make sure all the issues were fixed.

3. If you get the error message “cannot find source files”you need to have an ISO file mounted and need to specify where it is located with the below command. The ISO must be exactly the same version as the running OS.  An ISO of 10586.0 will not repair a running system of 10586.35 because it has additional updates and files.