Scanner driver initialization problem

[CHFFT_1941]

I have further information.

If the batch file is started when the printer/scanner is off, the WIA service fails to restart. Here is the console display:

C:\Windows\System32>net stop stisvc
.
The Windows Image Acquisition (WIA) service was stopped successfully.

C:\Windows\System32>timeout /t 3 /nobreak 1>nul

C:\Windows\System32>net start stisvc
The Windows Image Acquisition (WIA) service is starting........
The Windows Image Acquisition (WIA) service could not be started.

More help is available by typing NET HELPMSG 3523.

After this if, I check the status of the system (services.msc), I see "Starting".
This last 4-5 minutes and the status changes to "Running".

However HP scan still does NOT work!!!!

[Kuroi_Kenshi]

Hi @CHFFT_1941,

Thank you for the additional testing and for documenting your findings so thoroughly. The information you've shared is very helpful.

Based on your latest observations, it suggests that the issue is no longer limited to the WIA service itself. Instead, it appears that the HP scanner driver is not registering correctly with the Windows WIA subsystem during system startup, even though the service eventually starts.

To help narrow this down further, could you please check the following?

Verify the scanner in Device Manager

Press Windows + X and select Device Manager.

Expand imaging devices or printers.

Check whether the HP scanner appears normally after a reboot before restarting the WIA service.

If it shows a warning icon, please let us know the reported status or error code.

Test using Windows Scan

After a reboot, but before restarting the WIA service, try scanning with the built-in Windows Scan application.

If Windows Scan also fails, it would indicate that the issue affects the Windows imaging framework rather than only the HP Scan application.

If Windows Scan works while HP Scan does not, it would point more specifically to the HP scanning software.

Thank you again for the detailed diagnostics you've provided. Since you've consistently reproduced the behavior and identified that the WIA-HP LJ M139M142 (NET) 1.0 source disappears after every reboot, this is valuable information for further investigation.

I look forward to your findings.

Take care and have an amazing day ahead! 🚀

Best regards,

Kuroi_Kenshi

[CHFFT_1941]

Hi,
Thank you for your answers.

1)
I checked the device manager before restarting WIA.
NO warning icon is displayed.
Rem : depending if the scanner is on or off, I see 2 or 3 devices.

2)
I don't find the built-in Windows Scan application on my computer. BUT I tried other SW than HP scan (drawing programs).
I can select among different devices. Without having restarted the service, I don't have access to a device
allowing me to scan with 600dpi and with brightness and contrast control available (either not present or not working).

After having restarted WIA service I have access to all features.

Note that I see following devices (omitting USB devices):

--> HP LJ M139M142 TWAIN 2.4 (32-32) : Calls HP TWAIN (~ same kind of interface than HP scan) with several options and allowing 600dpi
--> WIA-HP LJ M139M142 (NET) 1.0 (32-32) : Calls another interface window, with brightness and contrast control and allowing 600dpi
- WIA-NPI78DC4F (HP Laserjet MFP M1 1.0) : Calls another interface window, without options and allowing only 300dpi

3)
Looking at the last post of https://h30434.www3.hp.com/t5/Scanning-Faxing-Copying/Scanner-driver-initialization-problem/m-p/9683...
I saw that the proble is not affecting only me....

Thank you for your help

[Kuroi_Kenshi]

Hi @CHFFT_1941,

Thank you for the update and for continuing to share your findings.

I appreciate you confirming that.

Device Manager does not report any errors before the WIA service is restarted.

The TWAIN interface remains available, while the WIA-HP LJ M139M142 (NET) 1.0 interface is unavailable until the WIA service is restarted.

Restarting the WIA service restores the missing scanning features, including 600 dpi support and the additional scan options.

Based on the extensive troubleshooting you've already completed, along with the additional testing you've shared, we've exhausted the software-based troubleshooting that can be performed remotely.

As the issue persists despite reinstalling the HP software, testing different installation packages, verifying the WIA service configuration, and reproducing the behavior consistently after reboot, I recommend having the printer inspected by an HP Authorized Service Center. They can perform additional hardware and firmware diagnostics to determine whether there is an underlying issue affecting scanner initialization that cannot be resolved through software troubleshooting alone.

Kindly follow this link to locate the nearest HP service center:    https://support.hp.com/us-en/help/service-center

Thank you again for documenting your testing so thoroughly. Your feedback is valuable and will help with further investigation into this behavior.

Take care and have an amazing day ahead! 🚀

Best regards,

Kuroi_Kenshi

[CHFFT_1941]

Hi,
Thank you for your answer.

As my printer/scanner is working perfectly after restarting WIA service (or immediately after SW reinstallation), I cannot imagine that the problem could be related to my printer.

Furthermore looking in the different forums and posts and seeing that other people have the same problem, I would point to an incompatibility between the driver and the WIA service.
Or perhaps a problem in the start sequence.

[Pallipurath]

Hi @CHFFT_1941 

Thank you for responding.

I understand your concern. Since the scanner works normally after restarting the Windows Image Acquisition (WIA) service or after reinstalling the HP software, the issue is likely related to the scanner driver or the Windows scanning service initialization rather than the printer hardware.

Perform a Clean Reinstallation of the HP Software

1. Disconnect the USB cable (if using USB) or disconnect the printer from the network.
2. Uninstall the HP printer software from Settings > Apps.
3. Restart the computer.
4. Open Print Management (or Print Server Properties) and remove any existing HP printer drivers.
5. Open Device Manager, enable View > Show hidden devices, and remove any old HP imaging devices if present.
6. Restart the computer.
7. Download and install the latest full-feature HP software for your printer model from the HP Support website. https://support.hp.com/in-en/drivers 
8. Reconnect the printer only when prompted.

Perform a Clean Boot

1. Press Windows + R, type msconfig, and press Enter.
2. On the Services tab, check Hide all Microsoft services.
3. Click Disable all.
4. Open the Startup tab and click Open Task Manager.
5. Disable all startup items.
6. Restart the computer and test scanning.

If the issue is resolved, a third-party application is likely interfering with the WIA service during startup.

Have a good day.

[CHFFT_1941]

Hi,

Thank you for your answer.

I followed scrupulously your instructions. The situation is exactly the same: when starting HP Scan, the driver is initializing continuously....

Thus following your conclusions, it's not a third party SW which is interfering with the WIA service during startup...

Perhaps the HP driver itself?

Note that de-installing one by one all the different HP SW and drivers installed by the HP installer takes a lot of time....
And I have done this a lot of times, without success....

I hope that this time, the obtained informations will help you finding the definitive solution.

[Pallipurath]

Hi @CHFFT_1941 

Thank you for responding.

Thank you for confirming the results and for your continued efforts in performing the troubleshooting steps. Based on the information provided, we will further investigate the HP Scan driver and WIA service interaction to identify the root cause and work toward a permanent resolution.

We will investigate this by reviewing the collected information, analyzing the HP Scan driver behavior, checking the interaction between the HP scanning software and the Windows WIA service, and verifying whether any driver components or services are failing during initialization. We may also review system logs, driver installation details, and scanner communication results to determine the exact point where the initialization process is getting stuck.

Have a good day.