WppRecorder.sys problem when updating Windows 10 from 1909 to 20H2

smartcooky · 18 Mar 2021

zbook said:

Are the Macrium backup images up to date?

Yes. Most recent backup was 5:31 am this morning

zbook said:

Make a new restore point:
Create System Restore Point in Windows 10

Ok

zbook said:

List and uninstall all non-Microsoft antivirus software

List and uninstall all non-Microsoft firewall software

List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software

There is no third party anti-virus, firewall or encryption software on this computer

zbook · 18 Mar 2021

The prior post was edited.

For all steps / tests make sure images are posted into the thread:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots

How to Upload and Post Screenshots and Files at Ten Forums

smartcooky · 18 Mar 2021

zbook said:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool
b) do not use the tool until it is communicated in the thread
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Question:

These links give two different selections for "Select individual settings from this full list".

Which list do I follow?

zbook · 18 Mar 2021

Please perform all of the drive tests first.

Then BIOS.

Then Windows Driver Verifier (WDV)

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

smartcooky · 18 Mar 2021

Thank you zbook for all this

This will be a job I start Saturday afternoon after work (that is the drive tests in post#10)

ETA: Managed to get this one done before the end of the day

Chkdsk /r /v

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x16cc1.
666112 file records processed.
File verification completed.
18324 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
36529 reparse records processed.
827930 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
36529 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 10126 unused index entries from index $SII of file 0x9.
Cleaning up 10126 unused index entries from index $SDH of file 0x9.
Cleaning up 10126 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
80910 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
666096 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
9101914 free clusters processed.
Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

116400228 KB total disk space.
79017676 KB in 266217 files.
233428 KB in 80913 indexes.
0 KB in bad sectors.
741468 KB in use by the system.
65536 KB occupied by the log file.
36407656 KB available on disk.

4096 bytes in each allocation unit.
29100057 total allocation units on disk.
9101914 allocation units available on disk.

Internal Info:
00 2a 0a 00 d8 4b 05 00 00 5e 09 00 00 00 00 00 .*...K...^......
b4 03 00 00 fd 8a 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

ETA: and this one

Sfc /scannow

Microsoft Windows [Version 10.0.18363.1441]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

ETA: and this one

Microsoft Windows [Version 10.0.18363.1441]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>DISM /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1316

Image Version: 10.0.18363.1441

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

zbook · 18 Mar 2021

Chkdsk /r /v C:

Code:

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

Many tests can be run tests overnight.

Please reboot into safe mode as a trial and error step to run each:
Boot into Safe Mode on Windows 10

Upgrade_failure_info.bat - Click here to go to the BSOD batch repository to download and run this batch file.

V2: https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html#V2

smartcooky · 19 Mar 2021

zbook said:

Please reboot into safe mode as a trial and error step to run each:
Boot into Safe Mode on Windows 10

Upgrade_failure_info.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Same problem - throws error, file does not appear in stated location

Tried in safe mode. The command prompt window just flashes and moves up and down the desktop but doesn't do anything

zbook said:

V2:

zbook said:

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html#V2

Already did this in post #9. Do you want me to do it again?

zbook · 19 Mar 2021

For any script that had failed during normal boot > try the script in safe mode.

smartcooky · 19 Mar 2021

zbook said:

For any script that had failed during normal boot > try the script in safe mode.

See first part of post 17

zbook · 19 Mar 2021

Please post any new error messages / codes for V2 in safe mode.