@SimBur2365
I can appreciate your obvious superior knowledge on the inner workings of Microsoft's complex relationships. I also understand that there complex relationships are very likely required for security and functional operation.
However your missive doesn't help the less that expert user understand how they can resolve the situation, as there are no specific, detailed, and clearly defined steps listed to resolve the issue.
With all due respect, I realize your statement might resolve it for an experienced software engineer, familiar with the inner workings of the global Microsoft system, but for the vast number of users who do not have that skill set, what you have written does not offer a concrete, workable solution.
As an aside, it appears you assume most individuals reading these are well versed on the system as you are. To be blunt, we aren't. Also to be blunt, documentation for solutions needs to be in layman's language as much as possible, and needs to be tested against an untrained individual. I see this VERY OFTEN in these types of forums, in which a solution is offered, and the author is so familiar with the systems that they inadvertently leave out key steps, which to them are second nature, but to the inexperienced user are NOT a typical option they would invoke. For instance, many times when a change is completed, the window needs to be "Saved". Many end users may not be familiar with the particular window, and may not complete the last step, negating al the previous work. I have found a series of step by step screen shots, with arrows or highlights of the critical operations to be accomplished in each step are helpful.
Again, with all due respect, I have little doubt that your paragraph does address the root cause and the solution. But without the kind of documentation I mention above, it does little to help the inexperienced user solve the problems, AND CREATES FURTHER FRUSTRATION ON THEIR END. Creating one more small negative public relations impression for Microsoft.
