-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Printers
- Printer Setup, Software & Drivers
- I can't reinstall the "Full Software Solution" for printer H...

Create an account on the HP Community to personalize your profile and ask a question
01-01-2022 10:46 AM
Hello,
As I faced weird problems while scanning recently using WIA (HP Scan and capture gave results in black and white, while I selected colours…on multiple computers running Windows 10), I decided to uninstall and reinstall the driver for my MFP printer HP LaserJet Pro M1217nfw.
I first uninstalled the full driver solution (in Control Panel\All Control Panel Items\Programs and Features).
I also uninstalled the printer driver packages in Control Panel\All Control Panel Items\Devices and Printers (under Print Server Properties) + uninstalled the scanner driver packages in the Device Manager under Imaging Devices.
Finally I removed the remaining obsolete drivers in C:\Windows\System32\DriverStore\FileRepository\ using the application Driver Sore Explorer
Then I rebooted and tried to reinstall the Full Software Solution (driver+software) using the option Configure the printer to connect to a new wireless network:
When it asked to connect the USB cable:
I connect the USB cable, the installer display "Wireless Configuration" for a few seconds and then fails (exit without any message):
There is an Application Error in the Windows event viewer:
Faulting application name: ProductInst64.exe, version: 2015.528.2.27012, time stamp: 0x55667afd
Faulting module name: ProductInst64.exe, version: 2015.528.2.27012, time stamp: 0x55667afd
Exception code: 0xc0000409
Fault offset: 0x00000000000fa059
Faulting process ID: 0x3efc
Faulting application start time: 0x01d7ff3023c9bb5e
Faulting application path: C:\FULL software and driver solution\v20180815 (2021-07-22)\extracted\ProductInst64.exe
Faulting module path: C:\FULL software and driver solution\v20180815 (2021-07-22)\extracted\ProductInst64.exe
Report ID: e7cadf4a-a32f-4e5b-871c-824b4bd67a51
Faulting package full name:
Faulting package-relative application ID:
Followed by a Window Error Reporting information:
Fault bucket 116040202976, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0
Problem signature:
P1: ProductInst64.exe
P2: 2015.528.2.27012
P3: 55667afd
P4: ProductInst64.exe
P5: 2015.528.2.27012
P6: 55667afd
P7: 00000000000fa059
P8: c0000409
P9: 0000000000000000
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CEB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DD7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E45.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E53.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EE0.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ProductInst64.ex_d466e123d0562fed7a7dc4b7c5fbb4ccfac7352_aff8fcb1_241d46c3-bde9-4d82-8fc7-72625b9a53ff
Analysis symbol:
Rechecking for solution: 0
Report Id: e7cadf4a-a32f-4e5b-871c-824b4bd67a51
Report Status: 268435456
Hashed bucket: c90e46a205c131d7d31fc099b78aedf4
Cab Guid: 0
If I select another option (like Configure to print using USB), the installer doesn't fail and install the drivers and software.
This issue only occurs if I select option Configure the printer to connect to a new wireless network. … and I need to use my MFP printer on my WiFi network 😕 I didn't change anything in my network.
Can somebody helps me please?
I've spend 3 days trying to solve this issue without success, even if IT is my job 😞
01-01-2022 11:12 AM
I will upload the log file ljp1100inst.log (located in folder C:\Windows\Temp\)
As messages cannot exceed 100000 characters here (and the log file content is > 250000) , I have to upload the log file somewhere…
01-02-2022 03:30 AM
Here is the content of the log file ljp1100inst.log (located in folder C:\Windows\Temp\) if I try installing the latest version of the HP LaserJet Full Feature Software and Driver (HP_M1130_M1210_MFP_Full_Solution-v20180815-10158769_1.exe):
https://uploads.lorcan.be/HP_M1217nfw_install_issue/v20180815/ljp1100inst.log
01-02-2022 03:52 AM - edited 01-02-2022 03:53 AM
… and here is the content of the log file ljp1100inst.log if I try installing the initial version (v3.0 - 2010-11-01) of the HP LaserJet Full Feature Software and Driver which was on the installation DVD:
https://uploads.lorcan.be/HP_M1217nfw_install_issue/v3.0_20101101/ljp1100inst.log
It's a shame I don't find what the installer actually does between line “Network singleton created” and line “dwExitCode”:
…
[ 1- 1-2022 17:15:14:678]- LOG(2724): Found wifi address 'NPIA04840' & '192.168.1.210'
[ 1- 1-2022 17:15:14:678]- LOG(2724): WifiCredentialsStep: Ping(192.168.1.210)
[ 1- 1-2022 17:15:14:678]- LOG(2724): NWISWrapper::Ping(192.168.1.210)
[ 1- 1-2022 17:15:14:678]- LOG(2724): Ping(192.168.1.210)
[ 1- 1-2022 17:15:14:678]- LOG(2724): Network singleton created
[ 1- 1-2022 17:15:19:944]- LOG(3374): dwExitCode = -1073740791
I suspect I removed something which corrupted the driverstore or something like that. However, the HP uninstaller should remove all the stuff and the installer should reinstall all the stuff 😕
I also tried sfc /scannow, ccleaner, in-place Windows upgrade (using the media creation tool)… I can't reinstall Windows just for this issue (there are too many applications and settings to reinstall/configure, just for a printer issue).
Does someone already faced such issues (and solved them)?
I REALLY NEED YOUR HELP !! 🙂
01-02-2022 06:42 AM
I've just tried installing the initial driver from the DVD (v3.0 - 2010-11-01) on a separate "clean" Windows (a separate Windows installed on a different partition of the same computer, where printer drivers were still not installed).
Instead of having:
[ 1- 1-2022 17:15:14:678]- LOG(2724): Network singleton created
[ 1- 1-2022 17:15:19:944]- LOG(3374): dwExitCode = -1073740791
… the installation continues and I get:
[ 1- 2-2022 11:32:06:651]- LOG(1EAC): Network singleton created
[ 1- 2-2022 11:32:06:671]- LOG(1EAC): Network started!
[ 1- 2-2022 11:32:06:671]- LOG(1EAC): GetIpAddrFromHostName()
[ 1- 2-2022 11:32:06:718]- LOG(1EAC): GetIpAddrFromHostName(IPv4)
[ 1- 2-2022 11:32:06:718]- LOG(1EAC): GetIpAddrFromHostName(blIpv6 = 0)
[ 1- 2-2022 11:32:06:770]- LOG(1EAC): Ping(192.168.1.210) #0
[ 1- 2-2022 11:32:06:785]- LOG(1EAC): Ping4()
[ 1- 2-2022 11:32:07:151]- LOG(1EAC): Ping SUCCESSFUL
[ 1- 2-2022 11:32:07:151]- LOG(1EAC): InstallSequencer() step = 17
[ 1- 2-2022 11:32:07:166]- LOG(1EAC): >> PUSH step INSTALL_WIFI_VIA_USB_STEP (17)
[ 1- 2-2022 11:32:07:166]- LOG(1EAC): SaveValueToHKey SeqStack
[ 1- 2-2022 11:32:07:166]- LOG(1EAC): --- InstallStep_WirelessViaUSB ---
[ 1- 2-2022 11:32:07:182]- LOG(1EAC): _PostProgressMessage hWnd=0xb0b66 msg=1125, param=230
[ 1- 2-2022 11:32:07:182]- LOG(1EAC): IsWifiNetworkConnected()
[ 1- 2-2022 11:32:07:182]- LOG(16C8): IDLCProgressDlg::OnCurrentProgressMsg()
[ 1- 2-2022 11:32:07:198]- LOG(1EAC): GetWifiNetworkInfo()
[ 1- 2-2022 11:32:07:198]- LOG(16C8): msg=Waiting for the printer to connect to the wireless network ...
[ 1- 2-2022 11:32:07:213]- LOG(1EAC): GetNetworkInfo(\\?\usbstor#cdrom&ven_hp&prod_smart_install&rev_1.0#000000000t201n0nsi1c&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b})
[ 1- 2-2022 11:32:07:219]- LOG(1EAC): EWSOpen()
…
You can see the full log file of the successful installation on the other partition (separate Windows installation on same computer) here:
https://uploads.lorcan.be/HP_M1217nfw_install_issue/v3.0_20101101_other_partition/ljp1100inst.log
I really wonder what I did wrong that prevents the “Network started” event to execute and makes the installation fail (dwExitCode = -1073740791) on my main Windows installation 😞
Does someone knows what the installer actually does to "start its network"? And what could prevent this action? I really don't understand what's happening 😕 😭
01-03-2022 12:15 PM - edited 01-04-2022 03:33 AM
I finally solved these issues! 😁
After the latest unsuccessful installations, I re-executed the Uninstall.exe included in each Full Feature Software and Driver version (v20180815, v5.0, v4.0 and initial v3.0) and rebooted each time the uninstaller completed.
I noticed that there were still remaining items which were not uninstalled or not deleted:
- The HP LaserJet Service was not uninstalled (and still appeared in the Windows Services)
- There were again drivers in the Windows driver store (C:\Windows\System32\DriverStore\FileRepository\)
- There were again HP files (.exe and .dll files), in the C:\Windows\System32\ folder
- C:\Program Files (x86)\HP\HPLaserJetService\ folder was still present and was not empty
- C:\Program Files (x86)\HP\Digital Imaging\ folder was still present and contains .exe and .dll files of the HP Customer Participation Program
- …
I performed a Disk Clean-Up again (run as Admin, checking option “Device driver packages”).
I removed the related driver packages in the WIndows Driver Store Repository (they came back after the unsuccessful installations) using the free tool Driver Store Explorer (note that I keep a back up of each folder before deleting them using the tool).
Reboot…
Then I searched every .msi files in each version, and I right-clicked each of them and select Uninstall (most of them were already uninstalled, except the HP LaserJet Service for instance):
- FaxInstaller.msi
- FaxInstaller64.msi
- hppLaserJetService.msi
- hppM1130M1210SeriesLaserJetService.msi
- hppusgM1130M1210Series.msi
- HPSSupply.msi
- M1210TBX.msi
- M1210TBXx64.msi
- marketresearch.msi
- netfx.msi
- PortMonitorInstaller32.msi
- PortMonitorInstaller64.msi
- ScanTo.msi
- ToolboxMX.msi
- ToolboxMX64.msi
- vcredist.msi
- …
(note: items in bold were still installed, even after executing the ntScrubber.exe mentioned below)
Reboot…
I removed the .dll and .exe files from the System32 folder (I saved a copy of them before deletion).
Then I noticed errors in the Windows Event Viewer coming from the PrintService (> Application and Services Logs > Microsoft > Windows > Print Service > Admin):
The print spooler failed to load a plug-in module HPM1210LM.DLL, error code 0x7E. See the event user data for context information.
It's normal, I just deleted this file in the previous step (this file was located in the System32 folder). However, that means that the print spooler tries to load this DLL, and I wondered why…
So I had a look at the Windows Spool folders and noticed there were still remaining driver files in them!!!
There were files in the following subfolders:
C:\Windows\System32\spool\drivers\x64
C:\Windows\System32\spool\drivers\x64\3
I didn't delete those files (I was afraid to do something even worse).
While searching the HPM1210LM.DLL file in each version of the Full Feature Software and Driver solutions extracted to my HDD, I finally found something interesting. This DLL file (and many others) was mentioned in a script file (\UTIL\ntScrubber\x64\ntScrubber.s) … which is a script to clean up files and registry. I should have opened and read this file earlier, because it helped me solving the issues!!!
I ran the ntScrubber.exe file (located in the same folder as the script file ntScrubber.s) for each version (newer to older) of the Full Feature Software and Driver solution. You have to reboot your computer each time ntScrubber completes.
**bleep**! There were still errors in the Windows Event Viewer coming from the PrintService:
The print spooler failed to load a plug-in module HPM1210LM.DLL, error code 0x7E. See the event user data for context information.
and a new one:
The print spooler failed to load a plug-in module mvtcpmon.dll, error code 0x7E. See the event user data for context information.
The reason: the script perfomed the cleanup (deleting files like HPM1210LM.DLL and mvtcpmon.dll) but failed to remove the HPM1210LM "monitor" key from the Windows registry, and it didn't even try to remove the "monitor" key linked to the file mvtcpmon.dll.
(Windows Print Spooler loads DLL files specified in registry subkeys under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors])
So I exported the following keys (and chilldren) and then I deleted them from the registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HPM1210LM]
"Driver"="HPM1210LM.DLL"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HPM1210LM\Ports]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Advanced TCP/IP Port Monitor]
"Driver"="mvtcpmon.dll"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Advanced TCP/IP Port Monitor\Ports]
There were also still remaining driver files in both folders:
C:\Windows\System32\spool\drivers\x64
C:\Windows\System32\spool\drivers\x64\3
I saved and removed these remaining files.
Reboot.
No more errors in the Windows event viewer.
I deleted all the files from temporary folders (%TEMP% and %WINDIR%\Temp).
Then I launched the installer (HpSetup.exe) from the oldest/initial version of the Full Feature Software and Driver which was on the installation DVD (v3.0 from 2010) … and IT SUCCEEDED !!!
Then I was able to update to the latest version (v20180815, published on 2021-07-22). Huraaah!
I hope it can help you if these issues happen to you 🙂
01-03-2022 12:47 PM - edited 01-04-2022 05:39 AM
For you information, performing the update of the full software solution doesn't update the driver for the scanner and that's "good".
Why? Because the WIA driver (version 1.0.1.58769 [2012-09-29]) included in newer versions of the full software solution (> v3.0) has bugs with scanning resolutions (scanning results are always "oversized" in 72 DPI, whatever the scanning resolution you selected [eg 300 DPI]).
I you install the initial version of the full software solution (v3.0) and then update it with more recent version of the full software solution, the most recent of the WIA driver (1.0.1.58769) included in the newer full software solution is NOT installed . It's the initial version (v1.0.1.19172 [2010-03-31]) which is used . The old version of the driver gives right correct scanning resolutions (matching the one you select).
By the way, the reason why I initially wanted to uninstall/reinstall the drivers completely is because I face weird behaviours while scanning (maybe since a Windows update?):
If I use HP Scan and Capture (coming from the Windows Store) with the oldest scanner driver, the results are (for a few weeks now) always in greyscale while I select the "color" mode!
If I use HP Scan and Capture with the latest scanner driver (installed manually), I can scan documents in colours but the output resolution is totally wrong (if I select 300 DPI, the result is "overscaled" in 72 PPI, which means that the total amount of pixels is correct but in a wrong resolution). I face exactly the same issue when scanning in Photoshop using WIA this the latest version of the scanner (for the same reason mentioned in the beginning of this message) .
If I use Photoshop with the initial driver, everting is OK (colours and resolution) but HP Scan and Capture scan results are now always in greyscale… I face the same problem with the application Windows Scan (also coming from the Windows Store). However I don't face the color/greyscale issue using the built-in Windows Scan and Fax.