New
#330
UPDATE 8/16:
"Known issues" updated. See first post for more details.
Tweet
— Twitter API (@user) View on Twitter
Tweet
— Twitter API (@user) View on Twitter
Tweet
— Twitter API (@user) View on Twitter
I'm not sure you can zap it for good but this might help: Turn On or Off Device Driver Automatic Installation in Windows 10
I don't see a specific HP download for my ProBook 450. Which service did you disable since it's not obvious when perusing the list of services? Have you checked your disk drive in Device Manager and can confirm that hpdskflt.sys is not assocaiated with the drive?
I have no issues running the PC with this device installed but it shouldn't be needed for a SSD based system. I've a suport ticket with HP and will report back.
-- Private user
-- Received the notice by Windows Update of the availability of the 1903 version, it was tried to install it.
The Problem: For 32 days in a row several times a day it was tried, always with 76% failure. Error: 0x80070003. Device drivers.
Tests and Trials:
- Run again and again the app: "Windows Update Troubleshooter".All recipes were applied from the most obvious to the most complicated.
Tests, not limiting:
- Execute checklist of the PC performances required by Microsoft for update to 1903
- Temporarily completely uninstall Malwarebytes.
- Clean starts
- No drive encryption
- Disconnect all peripherals except screen, keyboard and mouse.
- Disable all hidden controllers marked in gray.
- Check the disk with "chkdsk"
- Check the file system with "sfc"
- Check the system image with "dism" again and again
- Check the services related to Windows Update.
- Check that the PC hardware is adequate; To do this, install Windows 10 1903 on another blank disk, successfully.
- Clean the update software downloads every time.
- Tests with "Windows 10 Update Wizard" and with "Windows Update" alternately.
- Test with another machine on which 1903 was installed successfully.
- ................
Failed all the previous tests, try to test at the IT level.
- Analysis of the setuperr.log error files repeatedly.
- Discovery that the problem prior to the occurrence of the blockade was always:
"Mount WIM file C: \ $ WINDOWS. ~ BT \ Sources \ SafeOS \ winre.wim, index 1 to C: \ $ WINDOWS. ~ BT \ Sources \ SafeOS \ SafeOS.Mount. Error: 0x80070003 [gle = 0x000000b7]"
- Find out, on another computer, how you could mount winre.wim and check that this PC did not.
- Run SetupDiag.exe
- Find out that C: \ Windows \ System32 \ drivers \ wimmmount.sys is involved, which is called a driver but not from an external device and is not in Device Manager.
- Check that on a PC with 1903 it works.
- Waste infinite time until you find the following:
"If DriverPath is not system32 \ drivers \ wimount.sys, that is likely the issue. HKLM \ SYSTEM \ CurrentControlSet \ Services \ WimMount \ ImagePath should be pointed to system32 \ drivers \ wimmount.sys."
And, indeed, that was the mistake. As a result of having uninstalled "Macrium", this program left in the Registry (HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ WIMMount \ Imagepath.) Pointing the location of the wimmmount.sys driver to the directory where macrium was installed, which was NOT indicated by WindowsUpate.
Solved: Changing this path to "C: \ Windows \ System32 \ drivers \ wimmmount.sys", version 1903 could be installed without further incident.
Summary: Dozens of hours lost and headaches
Comment: Surprising that Microsoft leaves the quality of Windows 10 in the hands of the quality of the Macrium uninstall process.
@Steve C
Steve,
Take a look at this, it might help: Prevent Installation of a Device by Hardware ID
Maybe it's worth giving it a try.
I have been using this policy, to prevent update of my Intel RST driver. I spent a lot of time, testing for the best driver for my system and I don't want Microsoft to update it to the newer version (which I have already tested and it's not as good performance-wise as the one I installed). The policy has been working like a charm for the past 3 months!