We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

win10 pro Build 10525, 43.0a1 doesnt work

  • 1 antwoord
  • 1 het hierdie probleem
  • 6 views
  • Laaste antwoord deur 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.

All Replies (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 :(