Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

win10 pro Build 10525, 43.0a1 doesnt work

  • 1 відповідь
  • 1 має цю проблему
  • 6 переглядів
  • Остання відповідь від rosbeoll

more options

Yesterday windows offered to update Win20 pro with new Build 10525 ver and i upgraded that. Everything else works but my loved nightly(43.0a1) doesnt, it just gets stuckt and rolss over and over "waitingroll". Tried to re-install, but same result. Looks like it has no connection ? The workstation where from I´m sending the question, isnt the one with which I have the problem.

Yesterday windows offered to update Win20 pro with new Build 10525 ver and i upgraded that. Everything else works but my loved nightly(43.0a1) doesnt, it just gets stuckt and rolss over and over "waitingroll". Tried to re-install, but same result. Looks like it has no connection ? The workstation where from I´m sending the question, isnt the one with which I have the problem.

Усі відповіді (1)

more options

rosbeoll said

Yesterday windows offered to update Win20 pro with new Build 10525 ver and i upgraded that. Everything else works but my loved nightly(43.0a1) doesnt, it just gets stuckt and rolss over and over "waitingroll". Tried to re-install, but same result. Looks like it has no connection ? The workstation where from I´m sending the question, isnt the one with which I have the problem.

Sorry win 10 pro not 20 :(