- Local time
- 4:11 AM
- Posts
- 2,441
- OS
- Windows 11
Sorry if I'm saying anything already known, but it's been a while since I clean installed Windows 11 and the first time on 23H2. Having just installed on two laptops, the way it gets set up now is really not friendly. The main issue, after signing in with a microsoft account - is that you don't get to the desktop. It makes you wait (for a long time) while updates are being done - and it's not just the waiting - you also can't see which updates are being done.
With the first laptop I found it was on 24H2 when I finally got to the desktop (I don't know if was already on 24H2 or not as had only just purchased it and setting up for the first time - used laptop) but it did take an extremely long time doing updates. There were touchpad issues so I clean installed 23H2 and the touchpad was fine then,
The second one was an older laptop. Explained in another thread how I couldn't connect to wifi initially so when I finally got a connection, I signed in with a microsoft account again in (somehow thinking I wouldn't risk losing that connection being gone once on the desktop!) and had exactly the same thing. Not getting to the desktop due to very very long waits while windows installed updates. On this occasion I just cancelled everything and started again and set up with a local account instead.
I have never been that bothered about whether I signed in with a local or Microsoft account, but now I am! If you sign in with a local account, then you go straight to the desktop and you can see what updates are being done - which I think is sometimes part of the process of knowing what's on a laptop and what's going on. Also taking note of various bits of firmware and drivers installed.
Which means doing the oobe/bypass nro of course, and thanks to Bree, I now know you have to click on the command window before you can type on it.
So from now on I will always set up with a local account - as long as it remains possible. And then sign in with a microsoft account later - if wanted.
With the first laptop I found it was on 24H2 when I finally got to the desktop (I don't know if was already on 24H2 or not as had only just purchased it and setting up for the first time - used laptop) but it did take an extremely long time doing updates. There were touchpad issues so I clean installed 23H2 and the touchpad was fine then,
The second one was an older laptop. Explained in another thread how I couldn't connect to wifi initially so when I finally got a connection, I signed in with a microsoft account again in (somehow thinking I wouldn't risk losing that connection being gone once on the desktop!) and had exactly the same thing. Not getting to the desktop due to very very long waits while windows installed updates. On this occasion I just cancelled everything and started again and set up with a local account instead.
I have never been that bothered about whether I signed in with a local or Microsoft account, but now I am! If you sign in with a local account, then you go straight to the desktop and you can see what updates are being done - which I think is sometimes part of the process of knowing what's on a laptop and what's going on. Also taking note of various bits of firmware and drivers installed.
Which means doing the oobe/bypass nro of course, and thanks to Bree, I now know you have to click on the command window before you can type on it.
So from now on I will always set up with a local account - as long as it remains possible. And then sign in with a microsoft account later - if wanted.
My Computer
System One
-
- OS
- Windows 11
- Computer type
- Laptop
- Manufacturer/Model
- HP Pavilion 14-ce3514sa
- CPU
- Core i5
- Memory
- 16gb
- Hard Drives
- Samsung 970 evo plus 2TB
- Cooling
- Could be better
- Internet Speed
- 200mbps Starlink
- Browser
- Firefox
- Other Info
- Originally installed with a 500gb H10 Optane ssd