|
Last month, Microsoft officially announced Windows 11, which will be offered as a free upgrade to Windows 10 users. I'm sure they're all ready and willing to jump right on that
|
|
|
|
|
Will it run in windows 7 pcs?
I have read several places complaining about the min. requirements in hardware...
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Very true - Intel 8th gen and later[^], and whatever the equivalent for AMD.
Plus I imagine most of the Win7 machines out there don't have a TPM 2.0 chip.
I think the main upgrade path for most is a new machine.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: I think the main upgrade path for most is a new machine.
only IF you want to update.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
This might be a way to keep a forced upgrade at bay. Just keep using a machine that can't support Weleven.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
If you're a Win7 diehard and installed it on new hardware it'll work. OTOH if you're that much of a W7 diehard that you've ignored 8 and 10 are you really going to give a single ![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) about W11? 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Nope!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I am not a diehard because of windows 7, I just don't like to be forced to buy new hardware while everything was working perfectly on my machine.
I definitively ignored win 8 and 8.1 on purpose, because I didn't like it.
I had Win10 for a while in the old PC but it annoyed me so much that I went back to 7.
But although it still works well, there have been a couple of times where I didn't like some reactions while working... So I have bought new hardware.
Logically win 7 can't manage it properly and I am not really willing to invest a huge amount of time trying to tweak things so that it works properly.
I am running Win 10 in the new PC. I will have a fresh start, set everything up and do an image. Once Win 11 gets to SP1 I might consider checking it up, before... I don't think so.
I don't need to have the newest shiny hardware or software just for the sick of it. But once I decide to buy / do something I try to get something actual and with future perspective.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Researchers have bypassed Microsoft's emergency patch for the PrintNightmare vulnerability to achieve remote code execution and local privilege escalation with the official fix installed. As long as it doesn't break anything
A footnote to @Ravi-Bhavnani's item below
|
|
|
|
|
Hey, cut the criticism; their engineers are working hard at making rounded corners. Get your priorities straight!
|
|
|
|
|
Yeah, well.. As soon as they master the art of the smoothly cut corner - their updates won't keep failing.
|
|
|
|
|
Run > services.msc > Print Spooler > Properties > Stop
> Startup Type > Manual
Easiest way I know of to disable it while still letting you start it up when you actually need it.
|
|
|
|
|
Probably couldn’t hurt to set it to run as an account with few perms as well (IMO)
TTFN - Kent
|
|
|
|
|
Of course...
that patch came without new shiny icons, the system can't install it properly. 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
.NET 6 introduces new handy APIs that will make our development journey easier. Strangely, not the same list as the "Top 5" from the other day.
And I'm shocked that it took this long for them to create DateOnly and TimeOnly
|
|
|
|
|
Kent Sharkey wrote: DateOnly and TimeOnly
And the ORM writers frantically start pounding away at the keyboard to ensure that those types are backed by SQL date and time types! And so the dominos fall. 
|
|
|
|
|
Kent Sharkey wrote: DateOnly and TimeOnly
There they go crapping on extension methods I wrote for myself...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Almost all of those new features crap on extension methods I've written.
|
|
|
|
|
And they still don't support the null propagation operator in expression trees.
I wish it was standard that as new expression syntax is added to C#/.NET, expressions using that new syntax are required to be supported in Expression Trees. Not that all providers should be required to implement immediately, but to make it possible for providers to support it.
Currently, it's like LINQ supports an (not clearly documented) subset of C#.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
|
|
Older IT pros hardly make up a quarter of the overall workforce. "I'm just talkin' 'bout my g-generation"
|
|
|
|
|
Sadly that most likely means more frameworks, more bloatware, more code that can't be scaled.
What? Me, cynical?
|
|
|
|
|
Just because you're cynical doesn't mean you're not right 
It's also about time for a new paradigm to sweep through the young'uns - SOLID is getting so old
TTFN - Kent
|
|
|
|
|
How about SENILE:
Simple
Encapsulated
Necessary
Important
Low code (as in, minimal code)
Extensible
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
