Comment by snitzr 3 days ago Have they tried turning it off and back on again? 7 comments snitzr Reply vachina 3 days ago That’s what they did and that broke the wave. hinkley 3 days ago Sediment perhaps? thenobsta 3 days ago The forced update bricked the wave :( groby_b 3 days ago Yes. Techniker ist informiert. hulitu 3 days ago > Have they tried turning it off and back on again?Yes, but the bloody thing updated itself between reboots. But, don't worry, Microsoft will release a fix in a couple of years. gowld 3 days ago As you read in the article, yes, they did, and that's what caused the problem. twodave 3 days ago Well maybe they just need to jiggle the handle.
vachina 3 days ago That’s what they did and that broke the wave. hinkley 3 days ago Sediment perhaps?
hulitu 3 days ago > Have they tried turning it off and back on again?Yes, but the bloody thing updated itself between reboots. But, don't worry, Microsoft will release a fix in a couple of years.
gowld 3 days ago As you read in the article, yes, they did, and that's what caused the problem. twodave 3 days ago Well maybe they just need to jiggle the handle.
That’s what they did and that broke the wave.
Sediment perhaps?
The forced update bricked the wave :(
Yes. Techniker ist informiert.
> Have they tried turning it off and back on again?
Yes, but the bloody thing updated itself between reboots. But, don't worry, Microsoft will release a fix in a couple of years.
As you read in the article, yes, they did, and that's what caused the problem.
Well maybe they just need to jiggle the handle.