HPLaserjet P2035 not longer works after Windows 10 1709 update

[Tazgrump]

Attempting to print from any venue (Even Word 2016) causes a crash of application and nothing is left in queue.  Tried to reinstall latest driver (2015 date) it will not install. Also my 8600 ink jet on another machine also updated to 1709 16.299.19 has major lag before printing starts (direct USB connection). In both cases problems seen now, did not occur with lastest 1703.

Here is the information from Word 2016 crashing after printing is attempted to P2035. BTW the printer shows online and can print a test page manually from the external print controls on the printer. It is now a BOAT ANCHOR!

Log Name: Application
Source: Application Error
Date: 10/20/2017 11:21:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-TGJTKQU
Description:
Faulting application name: WINWORD.EXE, version: 16.0.4600.1002, time stamp: 0x59d395c8
Faulting module name: ntdll.dll, version: 10.0.16299.15, time stamp: 0x493793ea
Exception code: 0xc0000374
Fault offset: 0x00000000000f87bb
Faulting process id: 0x2cf4
Faulting application start time: 0x01d349d03403fa2b
Faulting application path: C:\Program Files\Microsoft Office\Office16\WINWORD.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a7734bd8-2dff-49f1-bec1-53cd7bbb080f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-20T18:21:53.378272100Z" />
<EventRecordID>712</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-TGJTKQU</Computer>
<Security />
</System>
<EventData>
<Data>WINWORD.EXE</Data>
<Data>16.0.4600.1002</Data>
<Data>59d395c8</Data>
<Data>ntdll.dll</Data>
<Data>10.0.16299.15</Data>
<Data>493793ea</Data>
<Data>c0000374</Data>
<Data>00000000000f87bb</Data>
<Data>2cf4</Data>
<Data>01d349d03403fa2b</Data>
<Data>C:\Program Files\Microsoft Office\Office16\WINWORD.EXE</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>a7734bd8-2dff-49f1-bec1-53cd7bbb080f</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Technology moves on, 10 steps backword for 1 step forward.

[teddux]

Who uses Windoze these daze?

Does it print directly?

[Tazgrump]

It prints directly with the Test page command. And with all apps in Win 8.1Pro and 10.12.6

I build computers the machine is my work machine and I have a proprietary Visual Basic program for analysis of bending stress for Tilt-up Concrete Walls and the Temporary wind bracing for same. I must run in windows even though the machine is Triple boot Windows 10 Pro 1709, Windows 8.1 Pro, and OSX 10.12.6. If the program was written in Real Basic I would be using the Mac side only although I need Bluebeam Revu Extreme to edit my PDFs of mys engineering details and Bluebeam does not make a comparable Mac based version. Acrobat does not come close. Further I also need  PDF Factory Pro's metrics setting to emulate the HP printer or the output PDF is not complete. This program also died when the HP 2035P driver went the day after the 1709 install. I had to reinstall  Pdf Factory Pro and it is back up. But the HP is dead on the Windows side in Win10 1709, I just did test prints from Win 8.1 and 10.12.6 and it prints flawlessly. It is like this driver is now not recognized in 1709. And it will not rerinstall. Something as far as printing has dramatically changed in 1709 and the lag on the other machien before printing starts for teh HP Officejet Pro 8600 Plus is also part of this.

The current driver for the 8600 is 28.8 and was released on Nov 13 2015.

The current driver for the 2035P is 20120627 and released on Jan 16 2015.

Both of these printers are Boat Anchors as far as HP is concerned, and the driver for the 2035P is not even a Win 10 driver it is a modified Vista driver doctored to run under 8.1 and 10 but not 1709.

[teddux]

File an RMA!

[Tazgrump]

They already said Buy a New printer and offered the loyalty reward which is more than Amazon.

Just throw away those toner cartridges...

[teddux]

They actually put back my deleted post, guess they trying to make us happy!!!

[SpTr]

Hey all! Old thread, but I figured out the solution and wanted to share it.

Running Windows 10 Pro, version 1803

1. Run the firmware update to the latest (ver20120105, Released Dec 10, 2013). I could not get the updater to work on Win10. I had to use an old Win7 laptop to update. The update process was VERY SLOW. Took two tries and I had to let it sit for ~10 minutes and it eventually worked. Might just be my ancient laptop.

Firmware update instructions list a prerequisite "must install the P2035 driver and be able to print to it". Might not be necessary but I did it anyway. Used the Win 7 P2035 driver (ver20120627, Released Jan 16, 2015).

2. Reset the printer to factory default
Turn the printer on, and while it is initializing press and hold both control-panel buttons at the same time until all the lights blink in unison.

3. Use the HP Universal PCL 5 driver instead of the P2035 driver
Had this driver saved on my network and tried it on a whim. Works perfectly!

In Device Manager it's listed as version 61.180.1.20062. In my folder it has the filename "upd-pcl5-x64-6.1.0.20062.exe".
I assume other PCL5 HP universal drivers might work if you can't find this exact version.