If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Common Problems when upgrading to 1803
This is a 21 page article on problems and fixes when upgrading to 1803
https://www.windowscentral.com/windo...lems-and-fixes |
Ads |
#2
|
|||
|
|||
Common Problems when upgrading to 1803
On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius
wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Thank you. Saved the entire page on disk just in case. -dan z- -- Someone who thinks logically provides a nice contrast to the real world. (Anonymous) |
#3
|
|||
|
|||
Common Problems when upgrading to 1803
On 05/14/2018 8:36 AM, slate_leeper wrote:
On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Thank you. Saved the entire page on disk just in case. -dan z- That is indeed a good article to keep handy. Thanks Arnie Rene |
#4
|
|||
|
|||
Common Problems when upgrading to 1803
On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius
wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. |
#5
|
|||
|
|||
Common Problems when upgrading to 1803
On 5/14/2018 12:06 PM, KenW wrote:
On Mon, 14 May 2018 11:49:07 -0400, EGK wrote: On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. +1 KenW If the updates provided something usefull, then I am all for updates like security updates. But who needs 3d paint, virtual reality, and some of the other worthless "improvements" -- 2018: The year we learn to play the great game of Euchre |
#6
|
|||
|
|||
Common Problems when upgrading to 1803
In article , Keith Nuttle
wrote: If the updates provided something usefull, then I am all for updates like security updates. and they do. But who needs 3d paint, virtual reality, and some of the other worthless "improvements" some do. |
#7
|
|||
|
|||
Common Problems when upgrading to 1803
EGK wrote:
On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. I wouldn't mind them breaking stuff, if I thought the feedback to their QA organization could result in real change and improvement. But it seems they're hell-bent on maintaining a constant level of brokenness. It boggles the mind why you would do that. They did delay RTM, because of a "drop-dead" issue in 17134 and had to fix it as 17134_1 before release. So at least they know what a drop-dead issue is. That seems to be the only level of defect they care about ("brickage"). And what they test in the Insider Edition, is not the same thing as is put in RTM. Microsoft loses the benefit of Insider testing, by doing that and forking streams at some point before release. And putting untested junk in there (new drivers). Having been in the business for a short while, and seeing what care goes into QA, I have to award Microsoft an "F", just from not learning from their mistakes. We always tried to do "lessons learned" from the usual stupid stuff that happens, at our place. Some of the last stuff we did was really good as a result. As a classic example, our staff wrote bundled backup software. They pretended it was production ready, and dog-fooded it (used the backup software to "protect" the departmental server). When the server went down a month later, the restore software didn't work (Picard facepalm). When queried, the responsible manager said "yeah, we didn't test that, too hard" or words to that effect. As you can imagine, in the "lessons learned", that example would be included as a cautionary tale for any high-flying developers who think "their **** doesn't stink" :-) We never had a repeat performance like that. Imagine if that software had gone to a customer, and their server went down at 2PM, and a fix had to be rushed out. Fortunately, it was only our own productivity that was affected. Paul |
#8
|
|||
|
|||
Common Problems when upgrading to 1803
On 05/14/2018 10:49 AM, EGK wrote:
[snip] Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. M$ was sued by God, who insisted on being the only perfect thing in existence. One of the conditions of the lawsuit was that they alter Windows to prove it's not perfect :-) -- A "pay per" might be a coin-operated cat simulator. |
#9
|
|||
|
|||
Common Problems when upgrading to 1803
On Mon, 14 May 2018 13:09:40 -0600, KenW
wrote: On Mon, 14 May 2018 10:06:50 -0600, KenW wrote: On Mon, 14 May 2018 11:49:07 -0400, EGK wrote: On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. +1 KenW I spent about 5 hours trying to get networking going on my 4 puters with some help. Got it working "on & off" on three. The Dell laptop = no freaking way. Three would work once and then give a different error the next time and another error. Back to flash sticks ! that's what ****ed me off too. They broke my network yet again. I don't care that homegroups are gone. I don't use that anyway but they again broke the ability to see all the computers on the network. |
#10
|
|||
|
|||
Common Problems when upgrading to 1803
On Mon, 14 May 2018 17:03:19 -0400, EGK wrote:
On Mon, 14 May 2018 13:09:40 -0600, KenW wrote: On Mon, 14 May 2018 10:06:50 -0600, KenW wrote: On Mon, 14 May 2018 11:49:07 -0400, EGK wrote: On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. +1 KenW I spent about 5 hours trying to get networking going on my 4 puters with some help. Got it working "on & off" on three. The Dell laptop = no freaking way. Three would work once and then give a different error the next time and another error. Back to flash sticks ! that's what ****ed me off too. They broke my network yet again. I don't care that homegroups are gone. I don't use that anyway but they again broke the ability to see all the computers on the network. 1803 works fine on my network here. |
#11
|
|||
|
|||
Common Problems when upgrading to 1803
On 14 May 2018, Ken Blake wrote in
alt.comp.os.windows-10: 1803 works fine on my network here. Mine, too. It sees and is seen by all Windows 7, XP, and Linux computers on my network. |
#12
|
|||
|
|||
Common Problems when upgrading to 1803
On Mon, 14 May 2018 15:51:04 -0600, KenW
wrote: On Mon, 14 May 2018 17:03:19 -0400, EGK wrote: On Mon, 14 May 2018 13:09:40 -0600, KenW wrote: On Mon, 14 May 2018 10:06:50 -0600, KenW wrote: On Mon, 14 May 2018 11:49:07 -0400, EGK wrote: On Sun, 13 May 2018 08:45:33 -0400, Arnie Goetchius wrote: This is a 21 page article on problems and fixes when upgrading to 1803 https://www.windowscentral.com/windo...lems-and-fixes Should be titled "Microsoft breaks windows 10... just because we can" ****ing assholes. +1 KenW I spent about 5 hours trying to get networking going on my 4 puters with some help. Got it working "on & off" on three. The Dell laptop = no freaking way. Three would work once and then give a different error the next time and another error. Back to flash sticks ! that's what ****ed me off too. They broke my network yet again. I don't care that homegroups are gone. I don't use that anyway but they again broke the ability to see all the computers on the network. You have to set the two Function Discovery Services to Auto-delayed I stopped and restarted those functions and that allowed the computers to see one another again but not sure if that will stick on a reboot. I'll try what you did if I have it happen again. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|