Windows 10 Announced - Released 29-Jul-2015

Technically, is there any difference how the upgrade is performed? I'm guessing the end result in either upgrade will be the same version of Win10 1803?

 

Thanks @stapp. That is good to know.

 

The result should be the same. I have done multiple machines and I have found that the Windows Update method does most of the work in the background and then reboots several times over about 15 minutes and then is done. The one I did this way took about 2 hours total but was only unusable for about those 15 minutes. Doing it from the ISO from Windows takes about 90 minutes and the machine is pretty much unusable the entire time. I've done about a half dozen with no issues whatsoever.

 

No problems with my second machine as well upgrading to 1803. For the first time, I probably won't have to resort to a clean install as in the past there were always minor issues with both machines...

 

Updated yesterday thru Windows update, took around an hour, no issues yet.

 

That machine does not want to upgrade. Looks like a clean install will be required.

Second machine updated without any issues at all and is up and running 1803 now.

 

Looks like 1803 is not in the volume licensing downloads yet. Anyone here know when that will happen by chance?

EDIT: Word on the street is May 7th. We shall see.

 

Win 10 1803 problem mega-thread here: https://www.reddit.com/r/Windows10/comments/8fxog1/windows_10_april_update_1803_megathread/ . I am not rushing to update to it.

Note: Make sure you check your system restore settings if you do update to ensure it is enabled.

 

Hey itman, highway mileage with 1803 varies a lot apparently. I was running 1803 17133 for almost a month on 5 systems with no problems whatsoever, and have now upgraded those 5 to 17134.1 successfully, as well as 2 other systems at 1709 previously. I know it is early yet, but there is nothing about 1803 that I don't like or that hasn't been solid for me. System configs vary from Celeron, low-end AMDs, high-end AMDs, to high-end Intel processors.

 

Same here, 1803 so far has been fine. Difference is I did a clean install. After almost 3 years of playing with 10, I have come to realize that a clean install is the only way to go. I'll try an upgrade, but I almost always resort to a fresh and clean install in the end. Upgrading is a flawed way of doing things IMO, something they should have realized a long time ago. Especially when one does it twice a year. Anyway, so far so good on my end.

 

ditto.

 

https://twitter.com/aionescu/status/989001645995495425

 

As of right now everything works perfectly in my W10 with 1803 except a couple of things.

Windows update: I rebooted a few times since the upgrade and W10 is not checking for updates automatically after a reboot. I even turned On Windows defender to see if it updates automatically and is not doing it. If I check for updates manually, the machine does the check successfully. Also, Windows defender updates manually successfully. There are no errors of any kind regarding WU in Events log. Should I run the Windows update troubleshooter?

Event log: Under Security, I am getting an auditing error for an Event 5061 every time I reboot or start the laptop. I think I also got it yesterday at least once long after booting. I think it has something to do with a certificate. Is anybody else getting this? Look under Security in Windows Event viewer.

Nombre de registro:Security
Origen: Microsoft-Windows-Security-Auditing
Fecha: 1/5/2018 00:55:43
Id. del evento:5061
Categoría de la tarea:System Integrity
Nivel: Información
Palabras clave:Error de auditoría
Usuario: No disponible
Equipo: DESKTOP-PE74VI6
Descripción:
Operación criptográfica.

Sujeto:
Id. de seguridad: S-1-5-19
Nombre de cuenta: SERVICIO LOCAL
Dominio de cuenta: NT AUTHORITY
Id. de inicio de sesión: 0x3E5

Parámetros criptográficos:
Nombre de proveedor: Microsoft Software Key Storage Provider
Nombre de algoritmo: UNKNOWN
Nombre de clave: Microsoft Connected Devices Platform device certificate
Tipo de clave: Clave de usuario.

Operación criptográfica:
Operación: Abrir clave.
Código de retorno: 0x80090016

Edit: I found people in another forum getting the 5061 error (probably OK to ignore), and someone else experiencing the same with Automatic Windows updates.

Bo

 

"Set defaults by app" under the default apps settings panel still crashes for me on multiple machines. I guess they're not going to fix it. At least not soon. Still not a deal breaker for me.

 

I dont have that problem but I read other people are also experiencing it.

Bo

 

No problem with it here either.

I am on Enterprise x64 1803 Build 17134.5

 

Tried the Clean Boot method and the upgrade succeeded this time but when I enabled the services and restarted I got two BSODs back to back, then the machine went into auto repair. I left the machine alone and came back expecting to have 1709 reinstalled but no, 1803 is up and running. I may end up doing a clean install on that machine anyway sooner or later.

No trouble at all on machine #3.

 

If you get further BSODs try BlueScreenView. It should be able to tell you, what driver is causing the crash.

 

Will do.

 

Ran SFC /SCANNOW from Admin CMD on the problem machine and it stopped at 28% and said it couldn't complete. I might try Tweaking.com - Windows Repair first before the clean install.

 

Did you try a chkdsk first? If not I would. Much faster and might fix it. If not the Tweaking.com solutions do work pretty well.

 

Yeah, I just ran that from within Windows Repair, no problem. SFC has got to 55% in Safe Mode so far. Will see if that finishes this time.

Edit: SFC finished this time - no problems.

 

I've had it with that machine. Every restart I'm getting a BSOD, even when it tried an auto-repair it BSOD. I'm going to clean install.

@roger_m ,

I know it would have been good to find what was causing the BSOD, I just don't have the patience, so didn't get around to downloading BlueScreenView.

 

Even with a clean install that machine had a BSOD with the first restart.