Windows 10 vs Windows 7
-
@EddieJennings said in Windows 10 vs Windows 7:
@WrCombs said in Windows 10 vs Windows 7:
everyone here hates Windows 10 like the plague, but I love it. To me, It's simple and easy to use.
I don't hate it, but the longer I've been a Windows user, I've become more interested in other options.
"The more you use Windows, the more you want to stop using Windows."
-
well, you upgraded late, so most weird stuff got fixed. That said you dont have choice anymore, its not like you can
install Windows 7 on ryzen or latest intel CPU due to rare circumstance of chipset incompatibility according to MS that we have to take very seriously, something about USB drivers not being able to work on Windows 7 and MS wont provide the drivers for Win 7, cause it is very bad and outdated system, and you need to jump on Windows 10.
-
That said, if your users really prefer Windows 7, likely this is interface related.
Consider getting a replacement shell for Windows 10 that makes it look like 7. Often that is all that they mean.
Or, if you have the flexibility, check out either Fedora with Cinnamon, or Mint Cinnamon for a Windows 7 like experience, but modern.
-
From an IT Pro perspective the problems with Win 10 generally seem to be that they've pooched many many updates and a lot of the scripting / automation that was working wonderfully in Win 7 appears to have been broken for no good reason.
-
We're flipping all of our clients over to Windows 10. It's a lot easier to maintain patch wise though the recent move to split-out .NET gives us a bit more complexity.
Whether Win7 or Win10 it's important to disable SMBv1. The following is PowerShell:
# Disable on Windows 10 Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol -Restart # Check Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol # Check and Disable on Windows 7 Get-Item HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | ForEach-Object {Get-ItemProperty $_.pspath} # Disable SMBv1 on Windows 7 Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 –Force Restart-Computer # Disable on Windows Server 2012 RTM # Check Get-SmbServerConfiguration | Select EnableSMB1Protocol # Disable Set-SmbServerConfiguration -EnableSMB1Protocol $false -Confirm:$False -
Weve got lingering Windows 7. But all new installs are 10. Big migration from 7 to 1903 planned for June.
-
I prefer the previous update method, and not the windows as a service updates.....every time it makes me want to bang my head against a wall... The start menu is better in windows 7, although task manager and copy progress are a lot better in windows 10..
-
I like both when they are running has a VM guest on my Fedora Workstation.:grinning_face_with_smiling_eyes:
-
As said, there is not much of a choice for new installs. You're either running Windows 10 or you're not running Windows.
-
I think there are pros and cons to each.
Patching has degraded on both, so there isn't a clear distinction on one being more stable when it comes to patching.
There are definitely better/more modern features in 10, but some of the stuff that I use take more clicks to access than it used to. They are hiding things that average people don't use, but I wish there were a setting or mode that would allow me to pick to bring those now hidden features to the foreground.
Windows 10 is faster on the same hardware, in my experience.
Customizing it is kind of a pain for administrators. Using xml files for customizing the start menu, task bar, etc is not super reliable.
In 1703 (maybe later versions, too), when you have a laptop with its lid closed, the start menu doesn't scale and is super tiny and cut off in certain sections. Pretty much unusable. -
@scottalanmiller said in Windows 10 vs Windows 7:
@EddieJennings said in Windows 10 vs Windows 7:
@WrCombs said in Windows 10 vs Windows 7:
everyone here hates Windows 10 like the plague, but I love it. To me, It's simple and easy to use.
I don't hate it, but the longer I've been a Windows user, I've become more interested in other options.
"The more you use Windows, the more you want to stop using Windows."
I dual booted Xubuntu recently, and wanted to full switch in light of new STEAM proton API, which is amazing it makes all games on steam for windows magically work on Linux, just make sure to download and choose latest BETA proton api.
The bad news, while the API works, and fixes the game. Most modern games come with proprietary anti-cheat engine, and that simply does not allow the game to play on multiplayer.
So I either need to change my games . or do Graphic card pass through which is too much of hassle even for tinkerer like me. However having said that I should stop wasting my time with games...
-
@scottalanmiller said in Windows 10 vs Windows 7:
That said, if your users really prefer Windows 7, likely this is interface related.
Consider getting a replacement shell for Windows 10 that makes it look like 7. Often that is all that they mean.
Or, if you have the flexibility, check out either Fedora with Cinnamon, or Mint Cinnamon for a Windows 7 like experience, but modern.
Classic Shell
-
@PhlipElder said in Windows 10 vs Windows 7:
We're flipping all of our clients over to Windows 10. It's a lot easier to maintain patch wise though the recent move to split-out .NET gives us a bit more complexity.
Whether Win7 or Win10 it's important to disable SMBv1. The following is PowerShell:
# Disable on Windows 10 Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol -Restart # Check Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol # Check and Disable on Windows 7 Get-Item HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | ForEach-Object {Get-ItemProperty $_.pspath} # Disable SMBv1 on Windows 7 Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 –Force Restart-Computer # Disable on Windows Server 2012 RTM # Check Get-SmbServerConfiguration | Select EnableSMB1Protocol # Disable Set-SmbServerConfiguration -EnableSMB1Protocol $false -Confirm:$FalseWhat do you mean split out .NET ?
You can install latest version of .NET on both systems, and the only split .net done was in 4.0 they made one full and one for client, then they realized it us mistake. and never did it again.
-
@Emad-R said in Windows 10 vs Windows 7:
@PhlipElder said in Windows 10 vs Windows 7:
We're flipping all of our clients over to Windows 10. It's a lot easier to maintain patch wise though the recent move to split-out .NET gives us a bit more complexity.
Whether Win7 or Win10 it's important to disable SMBv1. The following is PowerShell:
# Disable on Windows 10 Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol -Restart # Check Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol # Check and Disable on Windows 7 Get-Item HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | ForEach-Object {Get-ItemProperty $_.pspath} # Disable SMBv1 on Windows 7 Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 –Force Restart-Computer # Disable on Windows Server 2012 RTM # Check Get-SmbServerConfiguration | Select EnableSMB1Protocol # Disable Set-SmbServerConfiguration -EnableSMB1Protocol $false -Confirm:$FalseWhat do you mean split out .NET ?
You can install latest version of .NET on both systems, and the only split .net done was in 4.0 they made one full and one for client, then they realized it us mistake. and never did it again.
Windows 10 Update structure:
1: Servicing Stack Updates (Requires an acknowledgement prior to entry)
2: Latest Cumulative Update
3: Latest .NET Update for Windows 10 (I've not found a URL for this one yet)Meaning, .NET will not be delivered in the LCU anymore.
-
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
-
@scottalanmiller said in Windows 10 vs Windows 7:
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
From what I understand the throttling is being pulled off now.
-
@scottalanmiller said in Windows 10 vs Windows 7:
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
Also speaking of updates.
-
@JaredBusch said in Windows 10 vs Windows 7:
@scottalanmiller said in Windows 10 vs Windows 7:
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
Also speaking of updates.
FFS
Basically they just stated outright... Windows 10 isn't ready for production use. Which we knew, but they've made it official.
-
@scottalanmiller said in Windows 10 vs Windows 7:
@JaredBusch said in Windows 10 vs Windows 7:
@scottalanmiller said in Windows 10 vs Windows 7:
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
Also speaking of updates.
FFS
Basically they just stated outright... Windows 10 isn't ready for production use. Which we knew, but they've made it official.
Yeah, there was something on theregister or slashdot in the past couple of weeks about this. Makes me VERY happy that a) We're running WSUS at work to control this garbage and b) that I'm not the WSUS admin
-
@JaredBusch said in Windows 10 vs Windows 7:
@scottalanmiller said in Windows 10 vs Windows 7:
Speaking of Windows Updates. I literally just found my first Windows 10 machine that successfully detected 1809 and attempted to update. No word yet if it will be successful. But this is the VERY FIRST time that I've not had to use the media creation tool to get it to recognize that 1809 exists.
Also speaking of updates.
Hype, FUD, click-bait, whatever.
Jiminy Cricket folks sure love to blow their horns.
We've been on 1803 and our clients have and our contractor's clients have pretty much since it was released.
We've been deploying all new systems with 1809 patched and up to date because it just works.
I find that the primary problem with patching is a lack of regression testing by the folks doing the patching. For those that are, see www.patchmanagement.org and join the lists.
Microsoft has been "failing" at QA for patching for freaking years now. There's just too complex an ecosystem for them to cover all of the bases anyway so the idea that everyone's setup can be patched immediately is befuddling at best and suicidal at worst.
The reality is that we need to regression test and litmus test those patches to make sure they work for our systems. That's our responsibility not theirs.
Caveat: While the above is definitely a very not-so-humble opinion, Microsoft should have their collective defecation together at least for their own hardware line. But then again, folks install all sorts of stuff on their machines that seemingly take them off-spec so the above applies yet again.
The only patching issues we've had to date on the Windows 10 platform have been with users that took their machines out of deployment spec by installing whatever. Our in-spec Win10 deployments have been quite stable patch wise.
