Windows 10 Announced - Released 29-Jul-2015

The workaround is already known and mentioned here =

https://www.wilderssecurity.com/thr...ased-29-jul-2015.368734/page-191#post-2829623

(in both articles: from winaero & tenforums)

 

An upgrade can only be done from within Windows. If you boot from a DVD/USB, you can only do a clean install.

 

Krusty,

So you want to upgrade to 1903? Sorry if I've forgotten previous posts. Why are you so keen to have a DVD? I removed the optical drives from my computer as they were never used.

 

Yes, I'm on to that.

OK, I can see why with my multitude of posts how you could be confused.

1. I first tried upgrading Machine A, which installed fine but resulted in a black screen after first system restart. MR flash drive restored a working machine.
   
2. I tried burning MCT ISO to DVD x 2 machines = many, many fails.
3. Yes, I am currently attempting an upgrade on Machine B as I type because I found I can boot from a MR flash drive if it goes pair-shaped.
4. I wanted a DVD because the last time I completed a clean install using a flash drive my drive letters were all messed up. From memory, C drive wasn't what C drive should have been. I may consider a clean install at some point.

I hope that made things a little clearer. I do / did use my DVD drives to watch DVDs on both machines from time to time, so I'm keen to have them working.

While I've taken this thread so far OT I might as well continue... I booted to the MR flash drive on my Linux machine and imaged the drive. If I attempt a clean install of Win10 1903 on that machine and it fails like 1809 did, the MR flash drive should restore the Linux drive back to how it is now, right?

Thanks all for your patience.

 

1903 appears to have installed OK on Machine B, but after checking for updates and restarting as prompted, I'm on a black screen on this machine too. Only difference is this machine has spinning white dots so I guess I'll leave it alone to see if it does boot or not.

It doesn't look like that machine is going to boot now either, but I'll wait for a while.

Edit: Still just spinning white dots.

 

Well, that wasn't working. I was going to try a clean install from the flash drive I created earlier, but instead I tried a repair from that drive. Surprise, surprise. 1903 started!

Currently running sfc \scannow to see if that finds anything to repair.

 

Nothing to repair.

Another restart to see if Machine B boots = nope! spinning dots again.

Trying a clean install, while knowing I can restore from the MR flash drive if and when that goes pear-shaped.

 

The thread is for "Windows 10 Announced - Released 29-Jul-2015" or "The Krutsy issue" ?

Two pages already spent for this, why is not opened another thread for that specific issue?

 

To please @anon + I'm sure others, my last post here about 1903.

OK @guest , sure, a clean install worked but I got pretty sick of seeing search suggestions everywhere I typed. Windows 10 is not getting better, it's getting worse. 1809 clean install brought with it Edge automatically starting with Windows, then re-opening once closed, now the stupid search suggestions.

Any further correspondence regarding 1903 can be sent via PM. I won't post in this thread again.

Happy @anon ?

 

This is a HP SATA I drive; i.e. 1.5 Gb/s.

What SATA controller is the drive attached to? Many motherboards have multiple SATA controllers. My Gigabyte motherboard has 3 of them:

1. The primary SATA controller that is controlled by my AMD CPU chipset which supports up to SATA III drives; i.e. 6 Gb/s
2. A Gigabyte SATA controller controlled by Gigabyte chipset which supports up to SATA II drives; i.e. 3 Gb/s.
3. A JMicron SATA controller controlled by JMicron 362 chipset which supports up to SATA II drives; i.e. 3 Gb/s.

Now here is where it gets tricky. Win 10 changed how it handles non-HDD/SDD SATA devices. It treats them as SCSI devices. In other words, a RAID based driver is needed since that is the only one that supports SCSI.

For discussion purposes, let's assume your DVD drive is attached to your primary Intel chipset controller. Let's also assume your HDD/SDD is also attached to that controller. Finally, let's assume you are using either Intel's or the standard Win 10 ACHI driver for that chipset for increased HDD/SDD performance. You will have periodic system lockups and the like due to the HP DVD SATA I drive. This is because the SATA I DVD drive needs a SCSI; i.e. RAID driver, to function properly. If the above assumptions are applicable to your build, your options are:

1. Attach the DVD drive to another SATA controller other than the Intel chipset one. Hopefully, Win 10 will install the appropriate RAID driver for that chipset. I wouldn't count on that with hardware as old as yours.

2. If your motherboard only has the Intel chipset controller, you will have to uninstall the ACHI driver which in all likelihood bork your existing OS installation.

3. Unplug/remove or permanently disable in Win 10, the DVD drive and use it externally via a SATA to USB adapter. Or, purchase an external USB DVD drive.

 

Just some "facts" about my booting up issues with Windows 10 HOME after upgrading it to 1903.
It's that "Computers fail/hang on boot" problem.
After failing to start 3 times, Window 10 goes into the repair mode, and I can easily use my restore point to get back to the "normal" state.
What's interesting, the only one program "affected" and is being always removed from everywhere - Sandboxie 5.31-1

Go figure.

 

Anyway, upgrading while security softs are installed/running is bad practice.

 

Millions of users don't even use security softs, try upgrading with an HIPS active or with a system with most scripts binaries disabled or dissociated.
MS often uses unsigned files during updates or upgrades which triggera HIPS blocks and sandboxing.

It is not because you never had issues in that situation that nobody has and vice-versa.
The infinite issue thread here or other forums prove it.

 

Hi stapp,

I posted that link way back at #4737, but it looks like it might have been updated since then.

 

And here is my update on that Microsoft 1903 update.
After I've complained about "booting issues" on Windows 10 HOME after the 1903 update, this morning I experienced the same "failing to boot up" issue on my Windows 10 PRO at work.
Two different OS versions - Home and PRO.
Two different computer brands - Dell and ZT.
Two different locations, etc., but the same issue.

I've read all the "possible" issues with that update referenced in your link, but NOTHING is said about a serious boot-up issue.
Smart people at MS don't know about it?
Am I the only one chosen?

P.S. I'm glad that no Wilders Security members are affected by my issue.

 

To those having boot issues during/after the update, over the past couple of years of installing these updates almost always when I see this problem it is because of a Wi-Fi card. Removing it allowed the update to install as expected. In most cases these are work desktops and I did not put it back. This may be of no help, but I have seen it enough I thought it was worth mentioning.

 

I agree. I would disable this on one of the devices having boot issues and see it that resolves your boot issues.

I had like boot issues after every Win 10 Feature Update except for 1803. For 1803, I did an in-place upgrade for the first time and have had no issues with Fast Startup or anything else for that matter.

 

I don't have Fast Startup enabled.
I don't put any machines to sleep/hibernation.
(I've learned that lesson many years ago.)

My problem starts right after the Windows 10 sign appears on the screen and the "wheel" starts turning. In a few seconds, I can see only the "wheel" turning and turning permanently.
A good thing, after 3 "hard-shutdowns", Windows 10 automatically gets into that "repair mode", and using the advanced options, I use a restore point right after the 1903 update.

 

My computers don't have Wi-Fi cards.