• duplex (double-sided) unit may not be detected

    From J. P. Gilliver@21:1/5 to All on Sun Jun 22 23:00:05 2025
    SnVzdCB0aG91Z2h0IEknZCBtZW50aW9uIHRoaXMgaW4gY2FzZSBpdCdzIGZydXN0cmF0aW5n IGFueW9uZSBlbHNlLg0KDQpJIGhhdmUgYSBwcmludGVyIHRoYXQgY2FuIGRvIGRvdWJsZS1z aWRlZDogaXQncyBhIFNhbXN1bmcgNzc1LCBidXQgd2hhdCANCmZvbGxvd3MgbWF5IGFwcGx5 IHRvIG90aGVyIG1vZGVscy4gKEl0IGNhbiBldmVuIGRvIGJvb2tsZXRzOyBvYnZpb3VzbHkg DQp0aGF0J3MgcmVhbGx5IHBhcnQgb2YgdGhlIGRyaXZlciBzb2Z0d2FyZS4gW1JlY2VudCB2 ZXJzaW9ucyBvZiBBY3JvYmF0IA0KUmVhZGVyIGNhbiBkbyBib29rbGV0cywgaWYgeW91IHdh bnQgdG8sIGV2ZW4gaWYgeW91ciBwcmludGVyIGRyaXZlciANCmRvZXNuJ3QsIHNvIGlmIHlv dSB3YW50IGEgYm9va2xldCwgInByaW50IiB0byBhIFBERiB0aGVuIHByaW50IHRoYXQuXSkN Cg0KSSBpbnN0YWxsZWQgdGhlIHByaW50ZXIgdW5kZXIgV2luZG93cyA3IC0gSUlSUiwgSSB3 ZW50IHRvIGdldCB0aGUgZHJpdmVyIA0KKEhQIG5vdyBoYW5kbGUgU2Ftc3VuZyBwcmludGVy cyksIGFuZCBpdCBpbnN0YWxsZWQgYW5kIHJhbiBmaW5lLiBJIGV2ZW4gDQpwcmludGVkIHRo ZSBvZGQgYm9va2xldC4NCg0KKEJ5ICJib29rbGV0IiwgSSBtZWFuIGhhbGYtc2l6ZSAtIHBy aW50aW5nIGZvdXIgcGFnZXMgdG8gYSBzaGVldCwgaW4gdGhlIA0KY29ycmVjdCBvcmRlciB0 aGF0IHlvdSB0YWtlIHRoZSBvdXRwdXQgc3RhY2sgYW5kIGZvbGQgaXQuKQ0KDQpXaGVuIEkg bW92ZWQgdG8gdGhpcyBXMTAgbWFjaGluZSwgSSBhc3N1bWVkIEknZCBoYXZlIHRvIGZldGNo IHRoZSBkcml2ZXIgDQphZ2FpbiwgYnV0IG5vIC0gSSBqdXN0IGNvbm5lY3RlZCB0aGUgcHJp bnRlciwgYW5kIFcxMCBpbnN0YWxsZWQgdGhlIA0KZHJpdmVyLiAoT0ssIGl0IHByb2JhYmx5 IGZldGNoZWQgaXQgZnJvbSBzb21ld2hlcmUsIGJ1dCBJIGRpZG4ndCBoYXZlIHRvIA0KZG8g YmF0dGxlIHdpdGggc29tZSB3ZWJzaXRlLikNCg0KU28gLSBJJ2QgYmVlbiB1c2luZyBpdCBm b3IgYSB3aGlsZSAocHJpbnRpbmcgc2luZ2xlLXNpZGVkLCBzaW5jZSBJIHJ1biANCml0IG1v c3RseSBvbiBqdW5rIG1haWwsIGEgbGFyZ2UgcHJvcG9ydGlvbiBvZiB3aGljaCBpcyBvbmx5 IHByaW50ZWQgb24gDQpvbmUgc2lkZSEpLiBUaGVuIEkgd2FudGVkIHRvIHByaW50IGEgYm9v a2xldCAodGhlIGxpc3Qgb2YgVGh1bmRlcmJpcmQgDQprZXlib2FyZCBzaG9ydGN1dHMgc29t ZW9uZSBraW5kbHkgcG9pbnRlZCBtZSB0bykuIFNvLCBsb2FkIHNvbWUgcGFwZXIgDQpibGFu ayBvbiBib3RoIHNpZGVzIChpLiBlLiBub3JtYWwgcGFwZXIhKSwgYW5kIHNldCB0by4NCg0K VG8gY3V0IGEgbG9uZyBzdG9yeSBzaG9ydCwgaXQgd2FzIHVuYWJsZSB0byBwcmludCBkb3Vi bGUtc2lkZWQgDQoob2J2aW91c2x5IG5lZWRlZCB0aGF0IGZhY2lsaXR5IHRvIGRvIGJvb2ts ZXRzIC0gdGhvdWdoIHRoZSBBY3JvYmF0IA0KYm9va2xldCB1dGlsaXR5IHdpbGwgZG8gb25l IHNpZGUsIHlvdSB0aGVuIHR1cm4gb3ZlciwgYnV0IHlvdSBoYXZlIHRvIA0KZmlkZGxlIHdp dGggdGhlIG9yZGVyKS4NCg0KSSB0aGVuIF9ldmVudHVhbGx5XyAtIHBva2luZyBhcm91bmQg aW4gc2V0dGluZ3Mgc29tZXdoZXJlIC0gZm91bmQgDQoiZHVwbGV4IHVuaXQgLSBub3QgaW5z dGFsbGVkIiwgb3Igc29tZXRoaW5nIGxpa2UgdGhhdC4gVGhlcmUgd2FzIGEgDQpkcm9wLWRv d24ga2lzdCBbb2YgdHdvIG9wdGlvbnNdLCBhbmQgSSBjb3VsZCBzZWxlY3QgImluc3RhbGxl ZCIgLSB0cml2aWFsLg0KDQpCdXQgSSdtIHByZXR0eSBzdXJlIEkgbmV2ZXIgaGFkIHRvIHRl bGwgV2luZG93cyA3IHRoaXM7IGluIGZhY3QgSSBkb24ndCANCmtub3cgaWYgdGhpcyBwcmlu dGVyIGlzIF9hdmFpbGFibGVfIHdpdGhvdXQgZHVwbGV4IGFiaWxpdHkuIChJIGJvdWdodCBp dCANCnNlY29uZC1oYW5kLikNCg0KSnVzdCB0aG91Z2h0IEknZCBtZW50aW9uIGl0IC0gaXQg aGFkbid0IG9jY3VycmVkIHRvIG1lIHRoYXQgV2luZG93cyAxMCANCndvdWxkIHRoaW5rIHRo aXMgYXNwZWN0IG9wdGlvbmFsLCB3aGVuIDcgZWl0aGVyIGRpZG4ndCwgb3IgYXV0b21hdGlj YWxseSANCmRldGVjdGVkIHRoYXQgdGhlIHVuaXQgd2FzIHRoZXJlIC0gaW4gY2FzZSBhbnlv bmUgZWxzZSBpcyBnZXR0aW5nIA0Kc2ltaWxhcmx5IGZydXN0cmF0ZWQhDQotLSANCkouIFAu IEdpbGxpdmVyLiBVTVJBOiAxOTYwLzwxOTg1IE1CKytHKClBTC1JUy1DaCsrKHApQXJAVCtI K1NoMCE6YClETkFmDQoADQpFdmVyeW9uZSBsZWFybnMgZnJvbSBzY2llbmNlLiBJdCBhbGwg ZGVwZW5kcyBob3cgeW91IHVzZSB0aGUga25vd2xlZGdlLiANCi0gIkdpbCBHcmlzc29tIiAo Q1NJKS4NCg0K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Graham J@21:1/5 to J. P. Gilliver on Mon Jun 23 08:27:26 2025
    J. P. Gilliver wrote:

    [snip]


    I then _eventually_ - poking around in settings somewhere - found
    "duplex unit - not installed", or something like that. There was a
    drop-down list [of two options], and I could select "installed" - trivial.

    I've seen a similar problem with an HP Envy printer.

    Windows 10 laptop shows duplex unit is installed, and until recently it
    printed duplex just fine. Now for several weeks it has not - it prompts
    the user to turn the sheet manually then press continue. The user is
    not aware of having made any changes to any of the settings. The only resolution I can find is to remove and re-install the driver. Knowing
    that this may take some time and involve endless frustration the job has
    been postponed.

    The user also has a Windows 11 laptop. This shows exactly the same
    information in the "printer properties" screen, specifically that the
    duplex unit is installed. And this Windows 11 laptop prints duplex
    perfectly OK.

    So HP and M$ fight ...!

    --
    Graham J

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Louis Krupp@21:1/5 to J. P. Gilliver on Mon Jun 23 02:07:07 2025
    This is a multi-part message in MIME format.
    On 6/22/2025 4:00 PM, J. P. Gilliver wrote:
    Just thought I'd mention this in case it's frustrating anyone else.

    I have a printer that can do double-sided: it's a Samsung 775, but
    what follows may apply to other models. (It can even do booklets;
    obviously that's really part of the driver software. [Recent versions
    of Acrobat Reader can do booklets, if you want to, even if your
    printer driver doesn't, so if you want a booklet, "print" to a PDF
    then print that.])

    I installed the printer under Windows 7 - IIRR, I went to get the
    driver (HP now handle Samsung printers), and it installed and ran
    fine. I even printed the odd booklet.

    (By "booklet", I mean half-size - printing four pages to a sheet, in
    the correct order that you take the output stack and fold it.)

    When I moved to this W10 machine, I assumed I'd have to fetch the
    driver again, but no - I just connected the printer, and W10 installed
    the driver. (OK, it probably fetched it from somewhere, but I didn't
    have to do battle with some website.)

    So - I'd been using it for a while (printing single-sided, since I run
    it mostly on junk mail, a large proportion of which is only printed on
    one side!). Then I wanted to print a booklet (the list of Thunderbird keyboard shortcuts someone kindly pointed me to). So, load some paper
    blank on both sides (i. e. normal paper!), and set to.

    To cut a long story short, it was unable to print double-sided
    (obviously needed that facility to do booklets - though the Acrobat
    booklet utility will do one side, you then turn over, but you have to
    fiddle with the order).

    I then _eventually_ - poking around in settings somewhere - found
    "duplex unit - not installed", or something like that. There was a
    drop-down kist [of two options], and I could select "installed" -
    trivial.

    But I'm pretty sure I never had to tell Windows 7 this; in fact I
    don't know if this printer is _available_ without duplex ability. (I
    bought it second-hand.)

    Just thought I'd mention it - it hadn't occurred to me that Windows 10
    would think this aspect optional, when 7 either didn't, or
    automatically detected that the unit was there - in case anyone else
    is getting similarly frustrated!

    I'm running Windows 10, and I have a couple of duplex-capable printers.
    The online version of the user guide for the newer one is dated 2019,
    and the specs say it's compatible with Windows 10. The user guide for
    the older one is dated 2009, and the specs don't mention Windows 10,
    which as far as I can tell was released in 2015.

    The newer printer always shows up as having the duplex unit installed.

    The driver for the older printer sometimes "forgets" that the printer
    has a duplex unit installed, so I have to go into the settings like you did.

    My guess is that it comes down to a driver quality issue. Drivers for
    older printers might not get the same level of testing as drivers for
    newer, shinier ones.

    You might be able to write a PowerShell script that would wake up once
    in a while, call Get-PrinterProperty passing it the name of your
    printer, check to see if the Config:DuplexUnit property is set to
    Installed, and call Set-PrinterProperty to set it if necessary.

    Louis




    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <title>Re: duplex (double-sided) unit may not be detected</title>
    </head>
    <body>
    <div class="moz-cite-prefix">On 6/22/2025 4:00 PM, J. P. Gilliver
    wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:1039ud6$j1mi$4@dont-email.me">Just
    thought I'd mention this in case it's frustrating anyone else. <br>
    <br>
    I have a printer that can do double-sided: it's a Samsung 775, but
    what follows may apply to other models. (It can even do booklets;
    obviously that's really part of the driver software. [Recent
    versions of Acrobat Reader can do booklets, if you want to, even
    if your printer driver doesn't, so if you want a booklet, "print"
    to a PDF then print that.]) <br>
    <br>
    I installed the printer under Windows 7 - IIRR, I went to get the
    driver (HP now handle Samsung printers), and it installed and ran
    fine. I even printed the odd booklet. <br>
    <br>
    (By "booklet", I mean half-size - printing four pages to a sheet,
    in the correct order that you take the output stack and fold it.)
    <br>
    <br>
    When I moved to this W10 machine, I assumed I'd have to fetch the
    driver again, but no - I just connected the printer, and W10
    installed the driver. (OK, it probably fetched it from somewhere,
    but I didn't have to do battle with some website.) <br>
    <br>
    So - I'd been using it for a while (printing single-sided, since I
    run it mostly on junk mail, a large proportion of which is only
    printed on one side!). Then I wanted to print a booklet (the list
    of Thunderbird keyboard shortcuts someone kindly pointed me to).
    So, load some paper blank on both sides (i. e. normal paper!), and
    set to. <br>
    <br>
    To cut a long story short, it was unable to print double-sided
    (obviously needed that facility to do booklets - though the
    Acrobat booklet utility will do one side, you then turn over, but
    you have to fiddle with the order). <br>
    <br>
    I then _eventually_ - poking around in settings somewhere - found
    "duplex unit - not installed", or something like that. There was a
    drop-down kist [of two options], and I could select "installed" -
    trivial. <br>
    <br>
    But I'm pretty sure I never had to tell Windows 7 this; in fact I
    don't know if this printer is _available_ without duplex ability.
    (I bought it second-hand.) <br>
    <br>
    Just thought I'd mention it - it hadn't occurred to me that
    Windows 10 would think this aspect optional, when 7 either didn't,
    or automatically detected that the unit was there - in case anyone
    else is getting similarly frustrated! <br>
    </blockquote>
    <br>
    I'm running Windows 10, and I have a couple of duplex-capable
    printers. The online version of the user guide for the newer one is
    dated 2019, and the specs say it's compatible with Windows 10. The
    user guide for the older one is dated 2009, and the specs don't
    mention Windows 10, which as far as I can tell was released in 2015.<br>
    <br>
    The newer printer always shows up as having the duplex unit
    installed.<br>
    <br>
    The driver for the older printer sometimes "forgets" that the
    printer has a duplex unit installed, so I have to go into the
    settings like you did.<br>
    <br>
    My guess is that it comes down to a driver quality issue. Drivers
    for older printers might not get the same level of testing as
    drivers for newer, shinier ones.<br>
    <br>
    You might be able to write a PowerShell script that would wake up
    once in a while, call Get-PrinterProperty passing it the name of
    your printer, check to see if the Config:DuplexUnit property is set
    to Installed, and call Set-PrinterProperty to set it if necessary.<br>
    <br>
    Louis<br>
    <h1 data-chunk-ids="syntax,inputs,outputs,example-1-set-a-printer-property,asjob,cimsession,computername,confirm,inputobject,printername,printerobject,propertyname,throttlelimit,value,whatif"><wbr></h1>
    <h1 data-chunk-ids="syntax,inputs,outputs,example-1-get-printer-properties,example-2-get-printer-properties-for-all-installed-printers,asjob,cimsession,computername,printername,propertyname,throttlelimit"><wbr></h1>
    <br>
    <br>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J. P. Gilliver@21:1/5 to All on Mon Jun 23 14:26:42 2025
    T24gMjAyNS82LzIzIDk6Nzo3LCBMb3VpcyBLcnVwcCB3cm90ZToNCltdDQo+IE15IGd1ZXNz IGlzIHRoYXQgaXQgY29tZXMgZG93biB0byBhIGRyaXZlciBxdWFsaXR5IGlzc3VlLiBEcml2 ZXJzIGZvciANCj4gb2xkZXIgcHJpbnRlcnMgbWlnaHQgbm90IGdldCB0aGUgc2FtZSBsZXZl bCBvZiB0ZXN0aW5nIGFzIGRyaXZlcnMgZm9yIA0KPiBuZXdlciwgc2hpbmllciBvbmVzLg0K DQpTb3VuZHMgdmVyeSBwbGF1c2libGUuPg0KPiBZb3UgbWlnaHQgYmUgYWJsZSB0byB3cml0 ZSBhIFBvd2VyU2hlbGwgc2NyaXB0IHRoYXQgd291bGQgd2FrZSB1cCBvbmNlIA0KPiBpbiBh IHdoaWxlLCBjYWxsIEdldC1QcmludGVyUHJvcGVydHkgcGFzc2luZyBpdCB0aGUgbmFtZSBv ZiB5b3VyIA0KPiBwcmludGVyLCBjaGVjayB0byBzZWUgaWYgdGhlIENvbmZpZzpEdXBsZXhV bml0IHByb3BlcnR5IGlzIHNldCB0byANCj4gSW5zdGFsbGVkLCBhbmQgY2FsbCBTZXQtUHJp bnRlclByb3BlcnR5IHRvIHNldCBpdCBpZiBuZWNlc3NhcnkuDQo+IA0KTm8sIF95b3VfIG1p Z2h0IGJlIGFibGUgdG8gZG8gdGhhdCAtIEknbSBwcmV0dHkgY2VydGFpbiBJIGNvdWxkbid0 ISBOb3cgDQpJIGtub3cgd2hhdCB0aGUgcHJvYmxlbS9zb2x1dGlvbiBpcywgSSdsbCBqdXN0 IGNoZWNrIHRoYXQgc2V0dGluZyBpZiBJIA0KZXZlciBoYXZlIHRoZSBwcm9ibGVtIGFnYWlu LiBBcyBmYXIgYXMgSSBrbm93LCBpdCBuZXZlciBfY2hhbmdlZF8gLSANCldpbmRvd3MgNyBr bmV3IGl0IHdhcyB0aGVyZSAocHJlc3VtYWJseSBkZXRlY3RpbmcgaXQgYXQgaW5zdGFsbGF0 aW9uKSwgDQoxMCBkaWRuJ3QgKHByZXN1bWFibHkgbm90LCBkaXR0bykuDQoNCj4gTG91aXMN Cj4gDQo+IA0KPiANCj4gDQpKb2huDQotLSANCkouIFAuIEdpbGxpdmVyLiBVTVJBOiAxOTYw LzwxOTg1IE1CKytHKClBTC1JUy1DaCsrKHApQXJAVCtIK1NoMCE6YClETkFmDQoADQpBbGwg SSBhc2sgaXMgdG8gX3Byb3ZlXyB0aGF0IG1vbmV5IGNhbid0IG1ha2UgbWUgaGFwcHkuDQo=

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)