Jump to content


Possible Quiting to Desktop refresh bug

Win 10 Windows 10 Bug Refresh

  • Please log in to reply
23 replies to this topic

PhoinexFire #21 Posted 08 July 2016 - 09:04 PM

    Senior Master Sergeant

  • Member
  • 71 battles
  • 426
  • [DRACS] DRACS
  • Member since:
    12-05-2013
I'm going to take a guess, but when you go to your desktop, is your game putting you into matchmaking, leaving matchmaking, or leaving or entering a match? It might be because of those reasons,as the game is loading, and then will put you in. That's how it sometimes works for me.

Caecias #22 Posted 09 July 2016 - 02:40 AM

    Senior Master Sergeant

  • Member
  • 233 battles
  • 428
  • Member since:
    06-22-2016

View PostPhoinexFire, on 08 July 2016 - 04:04 PM, said:

I'm going to take a guess, but when you go to your desktop, is your game putting you into matchmaking, leaving matchmaking, or leaving or entering a match? It might be because of those reasons,as the game is loading, and then will put you in. That's how it sometimes works for me.

 

Thanks for asking for clarification...   this is about exiting the game from hanger; a simple quit to desktop / exit to desktop.  I never really go to the desktop while entering a Match; but for the record I sometime do collapse (minimize) while I am in queue, or even at the beginning of the battle, only to return successfully to the game, but that is not what I am referring to in my initial post.

 

Best,

C-

 


Edited by Caecias, 09 July 2016 - 02:40 AM.

 

 


Caecias #23 Posted 29 July 2016 - 06:50 AM

    Senior Master Sergeant

  • Member
  • 233 battles
  • 428
  • Member since:
    06-22-2016

Bumping for additional inquiry
 

 

Has anyone else experienced the issue at hand?


 

 


Caecias #24 Posted 22 August 2016 - 04:24 AM

    Senior Master Sergeant

  • Member
  • 233 battles
  • 428
  • Member since:
    06-22-2016

Bumping this with an update...

 

I have recently updated my Win 10 Pro to Win 10 Pro Anniversary (build 1607) and the issue seems to be eliminated for now.   It persisted for quite awhile with 1.9.5.3-4; did not experience it much with  1.9.5.5...  but had upgraded to the new build of Win 10 Pro in that time period as well.

 

 


 

 





1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users