I got the upgrade from 8.1 Pro last night: 1.
I got the upgrade from 8.1 Pro last night: 1. The OOBE experience ran twice. It rebooted half way through the first one to apply updates and then I had to do it all again. 2. It lost the product key and won't activate even though this is a genuine copy from MSDN. I guess I have to wait for a key from MSDN later today. Not end of the world but a pain point. If it isn't activated, hardly anything works now. 3. However that's all pointless as it hangs solid after 3-5 minutes reliably. That's not enough time to even roll a single windows update in so I'm shafted. This is a rock solid Lenovo X201 that has never had a single problem with any Windows release. It hasn't crashed once since I bought it new. Not impressed. Spent an hour rolling it back. I imagine, considering this was quality well tested hardware, that this is going to be nothing but hell for people. If even 1% of people have this experience, the media will blow big time and I'd hope that they do. Edit: on my Sony VPC-J1 AOI machine that fails with "Windows 10 upgrade failed" after pissing around for an hour. At least that didn't hose the machine.
Posted by batou on Jul 29, 2015, 8:32 AM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
NewThe biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
I got the upgrade from 8.1 Pro last night: 1.
I got the upgrade from 8.1 Pro last night: 1. The OOBE experience ran twice. It rebooted half way through the first one to apply updates and then I had to do it all again. 2. It lost the product key and won't activate even though this is a genuine copy from MSDN. I guess I have to wait for a key from MSDN later today. Not end of the world but a pain point. If it isn't activated, hardly anything works now. 3. However that's all pointless as it hangs solid after 3-5 minutes reliably. That's not enough time to even roll a single windows update in so I'm shafted. This is a rock solid Lenovo X201 that has never had a single problem with any Windows release. It hasn't crashed once since I bought it new. Not impressed. Spent an hour rolling it back. I imagine, considering this was quality well tested hardware, that this is going to be nothing but hell for people. If even 1% of people have this experience, the media will blow big time and I'd hope that they do. Edit: on my Sony VPC-J1 AOI machine that fails with "Windows 10 upgrade failed" after pissing around for an hour. At least that didn't hose the machine.
Comments (0)
No comments yet. Start the discussion.