It is not surprising that none of those ideas produced a result.
The reason the reply that doesn't produce a result is marked as the "Answer" is because the reply that doesn't produce a result was posted by a Microsoft engaged Support engineer "expert" and then the topic went idle for 5-10 days and when that happens another Microsoft engaged Support Engineer "expert" marks the reply that doesn't produce a result as the answer even if it is impossible to be the answer.
In this case it only took 7 days for the automatic answer marking nepotism to kick in:
That is how they choose run things in the MS Answers community. It is extremely, extremely unlikely that any reply from a Microsoft engaged "expert" marked as the "Answer" by another Microsoft engaged "expert" is really going to be the answer.
The sad truth is that the since the forum owners allow this nepotistic answer marking practice of one alleged "expert" looking out for another alleged "expert" to continue unabated, the MS Answers community is polluted with thousands and thousands and thousands of "Answers" that are not really answers at all.
It is also extremely unlikely that the Microsoft engaged Support Engineer "expert" is following this topic at all so I would not hold your breath waiting for a reply.
The best thing to do is start a new topic/thread/question about your particular issue so it will appear at the "top" of the list of new and unanswered questions. That will get you the most visibility and best eyeballs on the topic.