Windows 10: Feature upgrade to 1903 issue

My Dell Inspiron 5759 laptop started off with an early version of Windows 10 and automatic upgrades have updated it as MS required. I think it was 1809 that started giving me trouble, Windows would load up to the desktop, show the desktop shortcuts, many without icons, no taskbar shortcuts and only the system tray time and notification icons. The cursor was an arrow while over the desktop but a revolving blue circle while over the task bar. Repeatedly clicking the task bar resulted in the screen blinking and eventually Windows would complete its startup. Of course I got pretty sick of this so tried upgrading to 1903 to see if this would cure it. The upgrade failed and when I looked at the upgrade history I discovered that MS had already tried and failed to upgrade to 1903.

I used the creation tool to create a bootable USB stick with 1903 on it. Tried to install 1903 but got to the partitioning stage where it said it couldn't install on the selected partition because it was of the GPT style. Used shift F10 and ran DISKPART not fully appreciating that CLEAN really really does clean. Never mind, the partition I use only for data was well backed up.

The install went okay and all seemed well. But after I had installed a couple of applications, I got the same problem as before except that repeatedly clicking the task bar did not complete the loading. Tried running SFC /SCANNOW, it told me that there were some corrupted files and it had fixed them. Looked at the log it produced, it was massive and might as well have been written in Swedish Chef as far as I was concerned. However the laptop booted up okay but only once, then the problem appeared again.

That was the SHORT version of the story. I tried several installs, all with the same results, spent days on it. Eventually got sick of the whole thing and dusted off a 1703 cd and tried instng from that. Got to the partitioning stage and was told that it could not install on the partition because it was of the GPT style. Shift F10 didn't work this time. I knew that the bios was set to EUFI, so went looking on the web for answers. Learned that Secure Boot needed to be enabled, so did this but had to also disable legacy CD. This is the only (as far as I know) difference in the BIOS between the 1903 installs and the 1703 install. The install then went perfectly. Laptop started much more quickly than it did with 1903 and repeated shutdowns, startups and restarts seemed to result in the startup getting faster. Started instng random applications, repeatedly shutting down and starting after each one. So far it is a dream.

So, if you haven't got too bored to read this far, the questions are: can I keep 1703 running against the tsunami of MS upgrades, and if not, how do I install 1903 so that it actually works?

:)

 

Local profile issue after upgrading to 1903

Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken

 

Windows Feature Update 1903

Hi Sara209

Greetings! I am Vijay, an Independent Advisor. The steps which you have undertaken to block updates won't work for any feature update. Feature updates need to be blocked temporarily by using different steps.

But, I will suggest that you should not try to stop 1903 feature update. Let it happen.

Do let me know if you have any more question or require further help.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.