Trying to apply windows 10 updates

Docfxit · 28 Feb 2018

Here are the results:

zbook · 28 Feb 2018

There are surface or error scans.
See if any of these software applications can detect the drive and perform the scan:
a) Macrorit Disk Scanner Portable Download
b) HD Tune: Full error scan
c) HD Sentinel: click disk > surface test (this is available only after registration or paid editions)

Docfxit · 28 Feb 2018

a) Macrorit Disk Scanner Portable Download
Results are below.

b) HD Tune: Full error scan
Doesn't recognize the drive

c) HD Sentinel: click disk > surface test (this is available only after registration or paid editions)
Recognizes there is a c: but doesn't recognize the drive.

Thanks,

Docfxit

Docfxit · 02 Mar 2018

Could someone please give me some feed back on the last in place upgrade on post #39?

Thanks,
Docfxit

Bree · 02 Mar 2018

Docfxit said:

Could someone please give me some feed back on the last in place upgrade on post #39?

I've not needed to analyse upgrade errors (luckily I've had none so far) so probably can't help much - except to note that it was an attempt to upgrade 1607 to 1709, as shown by setupact.log.

Code:

2018-02-28 11:54:58, Info                  MOUPG  SetupHost: Setup build version is: 10.0.16299.246 (rs3_release_svc.180131-1918)
...
2018-02-28 11:54:58, Info                  CONX   Host OS version: 10.0.14393.0

I do however know where to look should I have problems in the future.

This is a detailed document on resolving upgrade problems, covering analysing log files and upgrade error codes. There are fixes and mitigations listed for each error code. It's a bit technical, but covers most things you may need.

This topic contains a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade.

https://docs.microsoft.com/windows/d...upgrade-errors

Superfly · 02 Mar 2018

Docfxit said:

Could someone please give me some feed back on the last in place upgrade on post #39?

Thanks,
Docfxit

The only noteworthy info in the setup error log (the error codes are not specific) is the "Did not find hard disk space needed" entry - this may indicate a corrupt System Reserved partition. WU inserts boot files there for upgrades and some updates (?kernel related stuff) - check that it's OK with chkdsk and it has suffcient free space.

Win 10 normally has good driver compatibility in RTM.

(Not sure what the other logs are for... lots of generic info?)

Bree · 02 Mar 2018

Superfly said:

...Not sure what the other logs are for...

As I said, I've not had to delve into them myself, but if you need to they are described here in the document I linked to in post #45, along with how to analyse them.

Superfly · 02 Mar 2018

Bree said:

As I said, I've not had to delve into them myself, but if you need to they are described here in the document I linked to in post #45, along with how to analyse them.

Well I'm not going through 525 965 lines (of faff) in the setupact log - even a search does not find the error code - besides I find it hard to believe a basic driver like a notebook graphics can be the cause.

Good info though.. thanx.