[1607, au] RISO Driver

[Michael]

Hi all,

 

Has anyone successfully managed to get RISO's drivers working in a 64Bit environment? They're issuing self-certified Authenticode drivers which are not WHQL certified. Microsoft (reading up on things), are essentially making it mandatory for all drivers to be signed (moving forward), with each new edition of Windows 10.

 

Just curious to know what my options are, or is it literally a case bouncing it back to them asking for them to be WHQL certified?

[Steve21]

I don't know if it's changed in the latest releases, but you used to be able to disable drive checking, install it, then re-enable it and it'd accept them as it's already installed, but basically yes going forwards you need proper ones

 

Might be worth a test if you get a min on a machine.

 

Steve

[sted]

it works but everytime the driver is installed on a new pc you get a yellow box popup in the taskbar (unfortunately it dosent open and people dont see/ignore it) and then the driver dosent install. If you click the i want to install it button it works fine but its flipping annoying. Ithink its a signed driver its just not the right type of driver iirc if you look at the print management console theres a column where every other driver says yes riso drivers say no (iirc its packaged)

[Michael]

Thanks chaps - looking at a few websites, this is generally the procedure on how to install unsigned drivers -

 

"Windows 10 enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement.

 

- Click the Start Start menu and select Settings.

- Click Update and Security.

- Click on Recovery.

- Click Restart now under Advanced Startup.

- Click Troubleshoot.

- Click Advanced options.

- Click Startup Settings.

- Click on Restart.

- On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.

 

Your computer will restart and you will be able to install non-digitally signed drivers. If you restart your computer again the driver signature enforcement will be re-enabled".

 

Problem is, you'd have to do this per machine and it doesn't stick!? It's because the drivers are not WHQL certified which is the root of all problems.

[Michael]

I've tested on a 64Bit instance of Redstone 1; the drivers will install with elevated rights, but on reboot, you're forced to re-add the printer and driver again. It's unworkable basically.

[sted]

I've tested on a 64Bit instance of Redstone 1; the drivers will install with elevated rights, but on reboot, you're forced to re-add the printer and driver again. It's unworkable basically.

 

i know its a pita but could you bake the drivers into your base image so they are already installed (granted only helps going forwards)

[Michael]

How do you mean by bake exactly? I think the issue is (hypothetically speaking), after a Sysprep Windows re-detects all devices, but will once again detect that the driver is not WHQL signed, so won't automatically install it.

 

The only possibility I can think of, is to install a cert which Windows recognises, (as that's what Authenticode is) - a driver signed by a CA, but I suspect Microsoft will want to enforce WHQL regardless going forward.

[sted]

How do you mean by bake exactly? I think the issue is (hypothetically speaking), after a Sysprep Windows re-detects all devices, but will once again detect that the driver is not WHQL signed, so won't automatically install it.

 

The only possibility I can think of, is to install a cert which Windows recognises, (as that's what Authenticode is) - a driver signed by a CA, but I suspect Microsoft will want to enforce WHQL regardless going forward.

 

by default windows removes drivers on sysprep but you can tell it not to (i used to do that when i just used wds for imaging set up a laptop install drivers sysprep pull image and then use that image on other laptops and they all had the right drivers

 

in theory you could add the printer manually on your "gold" image (probably via ip so you dont need to add it to domain etc) install the driver and it should survive a reboot/sysprep

[Michael]

Just been informed WHQL drivers for RISO will be released next month, so watch this space

[psydii]

Just been informed WHQL drivers for RISO will be released next month, so watch this space

 

Could it be true? A chill wind bloweth over hell indeed. We wait with baited breath as we have done each of these last dozen years.

Edited October 17, 2017 by psydii

[Michael]

The WHQL drivers have been released on the US site here

 

They installed on the server and deployed on the client as expected - no issues, but time will tell in the next few days!

[Edu-IT]

How do you find the Riso printers, aside from the drivers?

[psydii]

Fast. Cheap if you do the volume. Reliable too, if people are trained and the machines are kept stocked with paper by knowledgable sensible staff.

 

Interestingly the HP PageWide desktop printers offer the same per page TCO, but you’d burn through ten of them a year if you were doing volumes suitable for a Riso.

[MartinRouterKing]

Exactly as above!

 

Make sure paper is stored in a dry place! Make staff fill the trays with paper properly.

 

Tell them they must not change the trays from auto to manual.

 

Make sure staff are shown how to unjam the printer and put everything the way it should.

 

Most Riso problems are caused by user error.

[Michael]

How do you find the Riso printers, aside from the drivers?

 

Do you mean the models? You could contact a RISO leasing company.

[Michael]

Fast. Cheap if you do the volume. Reliable too, if people are trained and the machines are kept stocked with paper by knowledgable sensible staff.

 

Interestingly the HP PageWide desktop printers offer the same per page TCO, but you’d burn through ten of them a year if you were doing volumes suitable for a Riso.

 

From a machine perspective yes, from a driver perspective absolutely not (until the newly released signed drivers). I've had zero problems reported.