Windows 10: What do I have to do to reliably report a bug to Microsoft concerning windows 10 2004?

For a while, I have been receiving the error "Windows Resource Protection found corrupt files and successfully repaired them", but the error keeps occurring no matter how many subsequent restarts and sfc /scannow commands I perform. I checked the cbs.log file, and identified the files that sfc keeps flagging:
Repairing file \??\C:\WINDOWS\SysWOW64\\srmclient.dll from store
Repairing file \??\C:\WINDOWS\SysWOW64\\srmscan.dll from store

After doing some research, I found that these two files are related to Microsoft file server, and was able to determine that the issue is linked to the "RSAT: File Services Tools" Optional feature in the apps & features menu in settings. Installing this optional feature, for whatever reason, breaks sfc. Here is my theory: the file paths that sfc is logging for these two files does not appear to be a valid path. Even assuming that the "\\?\" at the beginning of the path is irrelevant as far as the path to the file is concerned, if you take a closer look and the file paths, you may notice that both of the file paths have, not one, but two"\" characters separating the file from its parent directory. This is not a typo. This is what is in the cbs.log file:


2020-10-04 22:55:47, Info CSI 00000207 [SR] Verifying 100 components

2020-10-04 22:55:47, Info CSI 00000208 [SR] Beginning Verify and Repair transaction

2020-10-04 22:55:47, Info CSI 0000020a [SR] Repairing file \??\C:\WINDOWS\SysWOW64\\srmclient.dll from store

2020-10-04 22:55:47, Info CSI 0000020c [SR] Repairing file \??\C:\WINDOWS\SysWOW64\\srmscan.dll from store

2020-10-04 22:55:47, Info CSI 0000020d [SR] Verify complete

2020-10-04 22:55:54, Info CSI 0000022b [SR] Beginning Verify and Repair transaction

2020-10-04 22:55:54, Info CSI 0000022c [SR] Verify complete

2020-10-04 22:55:54, Info CSI 0000022d [SR] Repairing 1 components

2020-10-04 22:55:54, Info CSI 0000022e [SR] Beginning Verify and Repair transaction

2020-10-04 22:55:54, Info CSI 00000230 [SR] Repairing file \??\C:\WINDOWS\SysWOW64\\srmclient.dll from store

2020-10-04 22:55:54, Info CSI 00000232 [SR] Repairing file \??\C:\WINDOWS\SysWOW64\\srmscan.dll from store

2020-10-04 22:55:54, Info CSI 00000233 [SR] Repair complete

2020-10-04 22:55:54, Info CSI 00000234 [SR] Committing transaction

2020-10-04 22:55:54, Info CSI 00000239 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired



I have verified that installing the RSAT: File Services Tools optional feature is what causes this issue: I performed a clean install of windows 10 2004 as a virtual machine, installed all available updates, and even recorded my screen as I performed the initial sfc scan to show that sfc returned no corruption on a clean install, then installed the RSAT: File Services Tools optional feature, and finally ran another sfc scan which displays the error upon completion of the RSAT: File Services Tools optional feature installation. You can watch the screen recording for yourself at the link below:


https://1drv.ms/v/s!AndRKxKyXo6Ag9EXi8H2Ziaz5RdBzA?e=j0r0t5


Furthermore, not only does Uninstalling the package not fix the issue, but a repair installation of windows does not either. The only way to get sfc to stop reporting the error is to perform a fresh install of windows.


I have been trying to bring this issue to Microsoft's attention since windows 10 2004 was released. I have left feedback in the feedback hub repeatedly, I even wasted hours of my time calling into Microsoft support and opening a case 1507818465. Yet, time and time again, these important issues are ignored, and to be honest, I have about had enough of being ignored. What do I have to do to report a bug to Microsoft? Do I have to do something extreme like create an automated process to repeatedly submit the same bug report to this forum or the feedback hub until they are acknowledged, because that appears to be the only course of action that I haven't yet tried and is something I am fully capable of implementing, considering I am an automation engineer. I would rather not do this, but normal methods aren't working. I hope that this will post will finally accomplish the goal of getting this information in front of the people who need to see it, but realize that the chances are slim to none, which will result in the automated postings.

:)

 

Hardware Error reported by windows 10 Reliability Monitor, very concerned.

Windows 10 1903 is still new too, so, future cumulative updates might resolve some of the issues you are currently seeing.

I would also encourage you send in a bug report so engineers are aware of the problem.

File a bug report; send me the short link so I can vote on it and bring it to the attention of the Windows engineers.

https://windows10.help/blogs/entry/54-how-to-su...

Information in the above link is sourced from a trusted Microsoft MVP blog.

 

Reliability Monitor - View All Problem Reports Empty

Hi Ryan,

Windows update can reset your system settings and could've affected the information on your reliability monitor. To help us scan and fix your concern, we suggest that you run an sfc scan. Here are the steps on how to:

• Press Windows
  
  
  key +
  X key.
• Click Command Prompt (Admin).
• Type in sfc /scannow.
• Press the Enter key.

Once done with the scan, try to re-launch your reliability monitor and check if information is now available. If the concern persist, you can restore from a system restore point by clicking this

link.

Let us know if you need further assistance regarding your reliability monitor concern.

 

Hardware Error reported by windows 10 Reliability Monitor, very concerned.

So for reporting this as a possible bug would I just copy and paste my initial post?

I would like to know what the details of the error the monitor recorded and if they point to a specific piece of hardware so I know what to replace.

I have tested the RAM with the windows memtest checker as well as a full run if the bootable usb app memtest 86 and the RAM tested OK with no errors found.

I am suspecting the motherboard however I would rather not have to replace it until I can upgrade my cpu and power supply at the same time.