Tuesday, 6 June 2017

This Is Going To Be A Short Post,

well my bit of it anyway, for two reasons,

firstly although Diana went out for some food shopping, I stayed in and waited for the computer technician to arrived, which he did, after an hour or so he admitted defeat, evidently Microsoft knows it has a problem and knew way back in March that it had a problem, in this article in Forbes

this is the message I received on the hour every hour, I chose next month, but every hour there it was back again, eventually I gave in, I wish I had not! from the article,

''Windows 10 is getting better but there is still a problem at its core with how it handles updates, Windows 10 will give you more control over your updates in the Creators Update but that doesn't help users with bad updates,''

and it gets worse on the 8th May Microsoft issued this for IT administrators. and warns, ''This topic contains technical instructions for IT administrators''

so no chance for me to sort it out then! I just hope someone at Wattana Computers has read the article, which as it happens runs to 28 pages with gems such as this, 

''Quick fixes

The following steps can resolve many Windows upgrade problems.
  1. Remove nonessential external hardware, such as docks and USB devices.
  2. Check all hard drives for errors and attempt repairs. To automatically repair hard drives, open an elevated command prompt, switch to the drive you wish to repair, and type the following command. You will be required to reboot the computer if the hard drive being repaired is also the system drive.
    • chkdsk /F
  3. Attept to restore and repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed. For more information, see Repair a Windows Image.
    • DISM.exe /Online /Cleanup-image /Restorehealth
    • sfc /scannow
  4. Update Windows so that all available recommended updates are installed.
  5. Uninstall non-Microsoft antivirus software.
    • Use Windows Defender for protection during the upgrade.
    • Verify compatibility information and re-install antivirus applications after the upgrade.
  6. Uninstall all nonessential software.
  7. Update firmware and drivers.
  8. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
  9. Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.

Upgrade error codes

If the upgrade process is not successful, Windows Setup will return two codes:
  1. A result code: The result code corresponds to a specific Win32 error.
  2. An extend code: The extend code contains information about both the phase in which an error occurred, and the operation that was being performed when the error occurred.
For example, a result code of 0xC1900101 with an extend code of 0x4000D will be returned as: 0xC1900101 - 0x4000D.
Note: If only a result code is returned, this can be because a tool is being used that was not able to capture the extend code. For example, if you are using the Windows 10 Upgrade Assistant then only a result code might be returned.

Result codes

A result code of 0xC1900101 is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue.
To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the Resolution procedures section later in this topic.
Result codes can be matched to the type of error encountered. To match a result code to an error:
  1. Identify the error code type, either Win32 or NTSTATUS, using the first hexidecimal digit:
    8 = Win32 error code (ex: 0x80070070)
    C = NTSTATUS value (ex: 0xC1900107)
  2. Write down the last 4 digits of the error code (ex: 0x80070070 = 0070). These digits correspond to the last 16 bits of the HRESULT or the NTSTATUS structure.
  3. Based on the type of error code determined in the first step, match the 4 digits derived from the second step to either a Win32 error code, or an NTSTATUS value.
For example:
  • 0x80070070 = Win32 = 0070 = 0x00000070 = ERROR_DISK_FULL
  • 0xC1900107 = NTSTATUS = 0107 = 0x00000107 = STATUS_SOME_NOT_MAPPED
Some result codes are self-explanatory, whereas others are more generic and require further analysis. In the examples shown above, ERROR_DISK_FULL indicates that the hard drive is full and additional room is needed to complete Windows upgrade. The message STATUS_SOME_NOT_MAPPED is more ambiguous, and means that an action is pending. In this case, the action pending is often the cleanup operation from a previous installation attempt, which can be resolved with a system reboot.

Extend codes

Important: Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
Extend codes can be matched to the phase and operation when an error occurred. To match an extend code to the phase and operation:
  1. Use the first digit to identify the phase (ex: 0x4000D = 4).
  2. Use the last two digits to identify the operation (ex: 0x4000D = 0D).
  3. Match the phase and operation to values in the tables provided below.
  4. 2
The following tables provide the corresponding phase and operation for values of an extend code:
Extend code: phase
Extend code: operation

For example: An extend code of 0x4000D, represents a problem during phase 4 (0x4) with data migration (000D).''
and that is just a few of the pages! I still can not understand how a manufacture knows there is a huge problem with their product but still carries on insisting that customers should use it, rather like a car manufacturer knowing the brakes fail on a car but still sells them hoping to find a fix for the problem in a few months, but there it is, better the bugs from Microsoft than being ripped off by other companies, as soon as we get our computer back we will be back to normal.

No comments: