You came to Server Fault with a problem regarding WinRM. You went to ask a question, and received advice to search for similar questions to see if one of them would resolve your problem. You did this, and discovered an unanswered question that appeared similar to your problem. Then you posted a comment (as an answer) asking if the problem had ever been resolved.

This last is frowned on at SF and on the rest of the network. [Answers are reserved exclusively for answering the question][1], and comments for everything else, such as clarification. At the same time, there is a reputation requirement for comments, and we have [reasons to be strict on that][2].

So we move on to your primary question here about duplicates.

Over the years we have noticed that many people will often face exactly the same problem. Once a solution is identified for that problem, and written in an answer here, others can read the Q&A and possibly apply it to their own situations. Many questions are never posted at all because people were able to resolve their problems by reading an existing question and answers.

But sometimes people miss the Q&A (or don't search) and will post identical or nearly identical questions. In this case the community can mark such questions as duplicates of another existing question, the poster is notified of this and can [agree with the duplicate solving their problem or edit their question to show how it's different][3].

However, the community cannot mark questions as duplicates of another question _which doesn't have an upvoted or accepted answer_, like the one you reference. (A moderator can do this, but we generally do not unless the questions are identical and posted by the same person.)

In this case, if that is the only question you were able to find regarding your issue, I would expect you to post a new question, [with complete details][4], as though the other question didn't exist. You might wish to reference the other question and note that it is unanswered, though.

P.S. I did take a look at that question, and I note that it's odd that that error number is in decimal. Microsoft usually displays its error numbers in hexadecimal. If you convert that number, it comes out as 0x80338012. Perhaps you may find something relevant if you search for that.


  [1]: http://meta.stackexchange.com/q/118582/189912
  [2]: http://meta.stackexchange.com/q/214173/189912
  [3]: http://meta.stackexchange.com/q/250981/189912
  [4]: https://meta.serverfault.com/q/3608/126632