There is a guy on IRC who makes it a point to remind everyone every time he comes in, that the Windows 10 USB he got when Win10 released in 2015 is read-only and he can't update it.
Some, yes. Some bugs, maybe not. Clean install is always best practice regardless. But these random instances of core system DLL modules not being upgraded from 1803 to 1809 is very worrying. This stuff should have been picked up much earlier in the QA/Insider process.
makes u wounder if their even paying attention to that....looks like they put it together and dump on us to test completely and i understand is part of insider testing but this is getting completely ridiculous.
Just to let everyone know not to expect anything from Microsoft on Monday. 12 Nov. will be a very special Veterans Day, a National Holiday in the USA. It is a special day because it's the 100th Anniversary of the ending of WWI.
A bit Off topic but can anyone tell or confirm that whether the upgrade path from windows 7 ultimate using the Daz loader activator is still working to fetch a working Windows 10 pro license or not, if yes then which version of Windows 10 should I use for this & via which procedure, I mean in place upgrade or what
I wonder if any of the development teams at Microsoft working on windows 10 got fired or even reprimanded for releasing this last disaster 1809 it seems every week there is another bug found I think the last one was the activation problem what's next ?
The problem with the activation affected all the versions, not only 1809, it was a generalized problem.
More bugs: - In 1809's Defender, Device Security>Core isolation>Memory Integrity no longer works. It works just fine in RS4. Could be that they changed some requirements. But you don't just make a feature that was working fine no longer available.