kbrighton.4530

With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem. Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes. Nah it's a bug if you go back to 19645 it works perfect, They changed something in the kernel and it's causing a lot of programs to either crash or just not work when starting up. They know what it is they are just taking their sweet time to put the fix out in a new build. No, I get that. I was just saying that it was frustrating that ArenaNet support didn't acknowledge that it was a bug for close to a week in the ticket I had open with them. To be fair how would they know of a windows development bug? They really only have to support the official release and an insider version is not that and certainly not the fast ring, We take that burden on ourselves when we use it. You should check out the insider forums bugs get listed pretty quickThe frustration was mostly due to the fact that I was trying to report a bug to them and they ignored it, especially something that could become an issue for them in the future, should it be a breaking change in Windows, or that will be causing trouble for them for people who were running the same person. I provided logs (which were ignored), did a lot of debugging to try and figure it out myself, and validated that it was just an issue on the fast ring, and it basically fell on deaf ears in the support ticket. Any way, like I said, I'm just happy that it's been acknowledged, and that people won't have to go through the same level of frustration that I did, as they can just ask 'Are you running Insider? Known bug, it'll be fixed.'

With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem. Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes. Nah it's a bug if you go back to 19645 it works perfect, They changed something in the kernel and it's causing a lot of programs to either crash or just not work when starting up. They know what it is they are just taking their sweet time to put the fix out in a new build.No, I get that. I was just saying that it was frustrating that ArenaNet support didn't acknowledge that it was a bug for close to a week in the ticket I had open with them.

With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem.Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes.

With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue.

I was literally going back and forth with them for over a week before they finally acknowledged it was an issue. Thankfully, they seem to have some devs working on it.