Two Bugs in Sysprep: No Win Updates and CopyProfile Copies Search Suggestions

Question

We are using Windows 8.1 Enterprise 64-bit with Update 1.
I am not sure where (and even if) Microsoft accepts bug reports, but here are two that have been major annoyances for us for the past week.  They have workarounds, but they really need to just be fixed:
1. Windows Updates Do Not Work in Audit Mode
In Sysprep's Audit Mode, the Windows Update functionality does not work.  Updates can be manually installed or installed via PowerShell scripts, but the built-in update functionality does not work in Audit Mode.  This behavior is unexpected, detrimental
to deployments trying to use official tools, and contrary to the behavior of Audit Mode in Windows 7.
We have verified this behavior in multiple installations.
2. CopyProfile Unexpectedly Copies Start Screen Search History
The CopyProfile setting in the unattend.xml file mostly works as expected, but there is at least one effect that can result in unexpected behavior.
The Start screen in Windows 8.1 allows the user to perform searches, with categories such as "Everywhere," "Settings," and "Files."  When searching using "Everywhere," your search terms are stored at the following
location as LNK (shortcut) files:
C:\Users\<USERNAME>\AppData\Local\Microsoft\Windows\ConnectedSearch\History
When you use CopyProfile, these entries are transferred to the default profile, so all new users get the Administrator's search history, too.
In addition to this simply being annoying, there is a more serious issue: if any term searched by the Administrator account refers to files or settings that other users cannot access, then the user will receive an "Access is Denied" message.
For example, as the Administrator, I searched for "Device Manager" using the "Everywhere" setting on the Start screen.  A search-suggestion entry was created for this search term in the above folder path.  Then, I Sysprepped
the image using the CopyProfile setting, which copied the search suggestion to the default profile.  I then logged into Windows using a new standard user account, and "Device Manager" was a search suggestion by default.  When I clicked
on this search suggestion as a standard user, a message appeared indicating that access was denied.  At first, I thought I had a serious issue; it seemed to indicate, after all, that I had no access whatsoever to the Device Manager.  However, I could
still get to Device Manager by going through the Control Panel, so I did have access to the Device Manager itself.  Clearing the search history entirely eliminated this problem.
Sysprep, even with CopyProfile, should not copy the search history contained in the
ConnectedSearch\History directory.  Copying the search history is useless in any practical deployment, it is unexpected, and it gives the impression that Windows is malfunctioning when it is, in fact, working just fine.
Is there a way to report these (and other) bugs to Microsoft?

Answer 1

First, I sent an email to the author of PhotoME to inform him of the serious issues his addon caused with Firefox latest versions.
Now, for those of you who do not have the PhotoME addon and yet experience the same problem that I had and that I described above, I suggest the following strategy.
As PhotoME did cause these problems with Firefox latest versions, I am pretty covinved other addons probably might cause these problems too. Therefore, adopt the following method.
Test one addon at a time to see if this particular addon is behind your Firefox issues like the ones I had.
So, disable one addon only at a time. Then close your Firefox and restart it from scratch and see if you still have your Firefox problems. You must restart the Firefox browser from scratch. If you still have these Firefox problems, re-enable the disabled addon, restart your Firefox (again!) and repeat the same method for every single addon that you have.
Try to be selective by choosing first addons that are more likely to cause your Firefox problems such as not very well-known or not very popular addons (like it was the case for the PhotoME addon).
If this method works or if it does not work, report it on this web page so that others can be helped with your comments.
I hope this method will help you because I was really upset that I had these Firefox problems and I first thought it was the fault of Firefox, only to discover later that this PhotoME addon was the culprit and had caused me such upset.