Is it safe...? (Win10 to Win11 in-place upgrade)
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
No effect on VS at all - it went really smoothly and I had no problems. Provided your PC meets the Win11 requirements, it should work. But if you are even the least concerned, do a full image backup before you upgrade and you can restore if you get a problem / don't like it. I use AOMEI Backupper, and it does a brilliant job, even the free version! Backups are generally a good idea to have anyway, so upgrade immediately after your next one.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
No effect on VS at all - it went really smoothly and I had no problems. Provided your PC meets the Win11 requirements, it should work. But if you are even the least concerned, do a full image backup before you upgrade and you can restore if you get a problem / don't like it. I use AOMEI Backupper, and it does a brilliant job, even the free version! Backups are generally a good idea to have anyway, so upgrade immediately after your next one.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I personally would not do it, and would not base my actions on the success of one or a handful of people. Get yourself a new computer/laptop with Windows 11 installed. Now you have 2 computers, one with your beloved Windows 10 and one with Windows 11. That is how I would do it personally. Money is not an issue for me, so buying two computers is a walk in the park. If money is an issue, then follow Griff's advice especially the backup first part. good luck. cheers.
-
I personally would not do it, and would not base my actions on the success of one or a handful of people. Get yourself a new computer/laptop with Windows 11 installed. Now you have 2 computers, one with your beloved Windows 10 and one with Windows 11. That is how I would do it personally. Money is not an issue for me, so buying two computers is a walk in the park. If money is an issue, then follow Griff's advice especially the backup first part. good luck. cheers.
-
Better still, stick with Windows 10. After all, what does 11 actually give you that you do not already have?
It has an 11 on the about box. :laugh:
Jeremy Falcon
-
Better still, stick with Windows 10. After all, what does 11 actually give you that you do not already have?
Richard MacCutchan wrote:
what does 11 actually give you that you do not already have?
Nothing, actually. I needed a new computer as my Windows 10 box was feeling the age (2015), so I got a new computer with Windows 11 on it. Bells and whistles, a few added visuals, other than that, nothing.
-
Richard MacCutchan wrote:
what does 11 actually give you that you do not already have?
Nothing, actually. I needed a new computer as my Windows 10 box was feeling the age (2015), so I got a new computer with Windows 11 on it. Bells and whistles, a few added visuals, other than that, nothing.
That's probably the smartest method. I'm sure Win11 will have less issues on newer hardware. Personally, I never had any real issue except for a loud GPU fan, but my laptop isn't an old one. Eventually we'll have to upgrade due to Win10 not getting support, but that's waaaayy off (in PC terms).
Jeremy Falcon
-
Better still, stick with Windows 10. After all, what does 11 actually give you that you do not already have?
-
Some people of course need the ability to test their apps on both. But then having two computers with the different versions is the best way to do that anyways.
Or a VM.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I personally would not do it, and would not base my actions on the success of one or a handful of people. Get yourself a new computer/laptop with Windows 11 installed. Now you have 2 computers, one with your beloved Windows 10 and one with Windows 11. That is how I would do it personally. Money is not an issue for me, so buying two computers is a walk in the park. If money is an issue, then follow Griff's advice especially the backup first part. good luck. cheers.
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Thanks everyone for your replies! :rose: My Win10 box is less than 6 months old so I don't feel inclined to buy a new Win11 box. I'll therefore follow OG's advice and do an image backup before performing an in-place upgrade. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
If you are used to keep taskbar icon programs ungrouped, then I will suggest to do not upgrade. It's not possible yet to ungroup taskbar icons. And it looks it will never be possible. If I could, I would stick with Windows 10. Windows 11 has just more fancy icons and reduced productivity, not increased. Nice for home users, but has not a good UX for professionals/developers IMO.
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I've been upgrading Windows in-place on a weekly basis for several years, as my dev PC gets Windows Insiders builds (I started so I'd get the latest WSL builds as early as possible). In that time, I've had zero problems with the upgrade process and the problems I *have* had (a few BSODs) have been rare (for example, there was something about upgrading packages on my WSL Ubuntu install that caused a BSOD) and fixed in the next build. Anyway - my PC has seen Windows 10 versions from around when WSL was introduced in 2016 through to now when I'm running Windows 11 build 25276, which'll likely result in Windows 11 23H2.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I am lucky in this regard... I mostly work on my Dell Precision Laptop and it cannot be upgraded to Windows 11. Problem solved... ;)
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I've tried it twice so far and have gone back to Win 10. I don't remember what the problem was with the first attempt, but on the second try, things seem to work OK for about a week. Then a problem arose. I had been playing a game for about 3 days and on the 4th day Windows 11 decided that my game could no longer write save files to it's save file directory. All the fixes I could find on the web didn't fix the problem so I just restored Win 10 from my backup. I'm just going to wait to EOS before making the jump to Win 11. Hopefully, they'll have fixed their problems by then.
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
this: "My Win10 dev box " YOU SHALL NOT PASS!!!!! insert memes, I allow the forum to rape and pillage. I work for myself. When my laptop or machine dies, it is financially painful (I'm IT, HR, CEO, and the guy paddling like heck). You never, ever, never risk your dev laptop. Years ago, my children learned, you touch my laptop, I will adjust your attitude. My beloved wife would go to my laptop, and I'd ask her, "what are you doing?". I don't care what the answer was - mine was, "go do it on yours." No touchie <--- that's french. I love my wife - after 44 years, yeah I do. But Microsoft? Nah, don't think so. See another post I made - MS will delete your retreat path. Ask yourself - do you feel lucky?
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
this: "My Win10 dev box " YOU SHALL NOT PASS!!!!! insert memes, I allow the forum to rape and pillage. I work for myself. When my laptop or machine dies, it is financially painful (I'm IT, HR, CEO, and the guy paddling like heck). You never, ever, never risk your dev laptop. Years ago, my children learned, you touch my laptop, I will adjust your attitude. My beloved wife would go to my laptop, and I'd ask her, "what are you doing?". I don't care what the answer was - mine was, "go do it on yours." No touchie <--- that's french. I love my wife - after 44 years, yeah I do. But Microsoft? Nah, don't think so. See another post I made - MS will delete your retreat path. Ask yourself - do you feel lucky?
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Ha ha! I hear you, but I've always owned only one machine (my dev + personal PC). Noone else has access to it (I live alone) and there are very few apps installed on it aside from VS. My non-code data is ruthlessly backed up and my source code lives at MS. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
My Win10 dev box (an 11th Gen Intel i7 @ 2.80GHz, 32GB RAM, 1TB SSD NUC with zero bloatware) runs well and is the source of much joy, especially when building Android apps in C# using Visual Studio. I've been eyeing the MacOS-like rounded corners and the subtle window border shadows of the Win11 UI with envy. The only thing that's preventing me from upgrading (in place) is a perhaps irrational fear that VS will malfunction, or worse - stop working altogether. For those who've in-place upgraded their Win10 dev box to Win11, did it adversely impact Visual Studio? Am I over worrying? :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
