Windows 10: Update 1803 failed - leaves machine unusable

I also have trouble with Backup.
Windows 7 will not backup error code 0x81000033

I get a message that says " Windows skipped backing up system image because one of the critical volumes is not having enough free space. Free up some space by deleting unnecessary files and try again."
.
I cannot find any help on the web sites.

My problem isn't with Backup... my problem is with installation of the update.
Allan

I've no idea how to fix it, but the first thing I generally do when I've broken my Windows setup is to take a backup!
Then you can at least get back to where you are now if it goes even more wrong.
So I would use another computer to download Macrium Reflect Free, create a Macrium Recovery USB, then boot the broken Lenovo from that recovery drive, and backup the entire windows drive to an external drive.

It's only after I had a backup that I would try to recover it - perhaps the Rollback in System Restore if you haven't tried that?

Hi thompa ,

1) Find a flash drive that you can format ( > or = 8 GB )
2) Create a bootable Windows 10 iso:
Download Windows 10
3) Insert the Windows 10 iso bootable flash drive into any USB port
4) Power on the computer and click the applicable keyboard key so that you can boot to the BIOS boot menu
List of PC brands with their corresponding hot-keys
5) For the Lenovo repetitively click the the F12 key
6) Select the external USB HD if available so that you can boot to the iso
7) The iso may take 5 - 10 minutes to load while viewing the Microsoft Windows icon
8) In the left lower corner click repair your computer (do not click install)
9) Click troubleshoot
10) Click system restore (start with the oldest restore point and keep repeating as necessary until there are no more restore points) ( if system restore fails or if there are no restore points advance to the next step)
11) Click startup repair (if startup repair fails advance to the next step)

FOR THE NEXT STEPS PLEASE USE A CAMERA OR SMART PHONE CAMERA TO TAKE PICTURES AND POST IMAGES OF THE COMMANDS AND RESULTS INTO THE THREAD.
Use 7zip to organize the images. And use one drive or drop box to post share links into the thread.

12) Click command prompt> Administrator: X:\Windows\system32\cmd.exe > X:\Sources> type:
13) C:
14) dir
15) D:
16) dir
17) E:
18) dir
19) diskpart
20) list disk
21) detail disk
22) list volume
23) select disk 0
24) list partition
25) select partition 1
26) detail partition
27) select partition 2
28) detail partition
29) select partition 3
30) detail partition
31) select partition 4
32) detail partition
33) (If there are any additional partitions continue in a similar fashion for all partitions)
34) exit
35) bcdedit /enum
36) bcdedit | find "osdevice"
37) DISM /image:B:\ /cleanup-image /revertpendingactions
(for the above command change the letter B to the partition displayed in step #36)
38) sfc /scannow /offbootdir=B:\ /offwindir=B:\windows
(for the above command change the letters B to the partition displayed in step #36)
39) chkdsk /r
This may take many hours and typically displays ETA
reboot as needed

There are multiple additional troubleshooting steps depending upon the results of the above commands.
Please use a camera or smart phone camera to take pictures and post images into the thread. Use 7zip to organize the images and use one drive or drop box share links to post into the thread.

THanks Zbook - trying your instructions now...
A message windows opens with the message: 'It looks like you started an upgrade and booted from installation media. If you want to continue with the upgrade, remove the media from your PC and click Yes. If you want to perform a clean installation instead, click No.'
I take it I click 'Yes' which reboots the machine.
Proceeding to the next step....

Ok up to step 35) bcdedit /enum

which reported and a photo was taken and is the last in:
https://www.dropbox.com/s/rkb04it6ir...ovoAT.zip?dl=0

Step 36 would not execute, reporting 'Can't perform BCDEDIT | FIND "osdevice" parameters not correct.'

Hope that helps diagnose the issue!

thanks
Allan