Does Windows 10 cause this error?

Is Windows 10 the cause of this error?

https://answers.microsoft.com/static...completesignin

Is there a known solution?

--
David B.

David_B wrote:
Is Windows 10 the cause of this error?

https://answers.microsoft.com/static...completesignin


Is there a known solution?


Fuzzing the server on purpose, will get you no-where.

You can easily download a copy of VirtualBox from Oracle/Sun,

https://en.wikipedia.org/wiki/Virtualbox

In there, you can create a "New" guest OS. Insert
whatever Windows OS media you've got, do a test
install of Windows. It will remain functional for
at least 30 days. Then, go back and try to sign-in
to whatever server you were fuzzing from there, and
see if the response is new/different.

To have a comfortable amount of RAM for the purpose
of running a virtual machine, you need about 3GB of
memory. You can assign half to the Guest OS and
half to the Host OS. And still have enough RAM
in each for simple test cases.

To reduce installation time of the Guest, you can
get a VirtualBox "appliance" file, a .ova, from
Microsoft themselves. If you unpack the ZIP
and open the .ova with VirtualBox, it will populate
the settings for you. You'll still need to adjust the
network setting, and set it to "bridged", so you
can dial out to the Internet. This doesn't really
save all that much time, unless you want to
obtain a clean OS over and over again, it might
save time then.

https://developer.microsoft.com/en-u...vms/#downloads

By using virtual machines, you can live out your
fantasy of having a clean OS whenever you want it.
You can "remove and delete files", of the installed
appliance when ever you want, and unpack the .ova
multiple times. For a clean slate.

If a site has TOSsed you, then you might well need to
create another account. Then try your sign-in
test again.

Since you don't mention any other kind of web browser
side-effect, I have to conclude from the symptoms, this
is purely between you and Microsoft, and the status of
your account. In which case, the symptoms will reproduce
when you use a clean OS.

There's no point doing a Refresh or a Reset in Windows 10
host OS. Because right now, you haven't presented
any symptoms that say the OS is busted.

Paul

On 25/10/2017 17:22, Paul wrote:
David_B wrote:
Is Windows 10 the cause of this error?

https://answers.microsoft.com/static...completesignin


Is there a known solution?


Fuzzing the server on purpose, will get you no-where.

You can easily download a copy of VirtualBox from Oracle/Sun,

https://en.wikipedia.org/wiki/Virtualbox

In there, you can create a "New" guest OS. Insert
whatever Windows OS media you've got, do a test
install of Windows. It will remain functional for
at least 30 days. Then, go back and try to sign-in
to whatever server you were fuzzing from there, and
see if the response is new/different.

To have a comfortable amount of RAM for the purpose
of running a virtual machine, you need about 3GB of
memory. You can assign half to the Guest OS and
half to the Host OS. And still have enough RAM
in each for simple test cases.

To reduce installation time of the Guest, you can
get a VirtualBox "appliance" file, a .ova, from
Microsoft themselves. If you unpack the ZIP
and open the .ova with VirtualBox, it will populate
the settings for you. You'll still need to adjust the
network setting, and set it to "bridged", so you
can dial out to the Internet. This doesn't really
save all that much time, unless you want to
obtain a clean OS over and over again, it might
save time then.

https://developer.microsoft.com/en-u...vms/#downloads

By using virtual machines, you can live out your
fantasy of having a clean OS whenever you want it.
You can "remove and delete files", of the installed
appliance when ever you want, and unpack the .ova
multiple times. For a clean slate.

If a site has TOSsed you, then you might well need to
create another account. Then try your sign-in
test again.

Since you don't mention any other kind of web browser
side-effect, I have to conclude from the symptoms, this
is purely between you and Microsoft, and the status of
your account. In which case, the symptoms will reproduce
when you use a clean OS.

There's no point doing a Refresh or a Reset in Windows 10
host OS. Because right now, you haven't presented
any symptoms that say the OS is busted.

Â*Â* Paul


I've never come across that expression before! I'll ponder on what you
have said, Paul. Thanks.

https://en.wikipedia.org/wiki/Fuzzing




--
“Men occasionally stumble over the truth, but most of them pick
themselves up and hurry off as if nothing ever happened.� (Winston S.
Churchill)