New
#121
You don't have any issues with the disk partitions or the boot files. The problem is 100% within the Windows installation.
You don't have any issues with the disk partitions or the boot files. The problem is 100% within the Windows installation.
Hi Guys
I know exactly what's going on. In a nutshell the Avast is still stopping the laptop upgrading to Windows 10 April update.
“In cooperation with Microsoft we have identified an element of the latest Windows 10 1803 update that is incompatible with the Avast Behavior Shield, causing the aforementioned update to fail in some instances (related to a timing issue, Internet connectivity issue, etc),”
Avast Shares Fix for Broken Windows 10 April 2018 Update Machines
Removing Avast completely from the Registry might be a solution; then the update might 'complete' in the fashion that it was meant to.
If you have files backed up then you can always clean install.
Alternatively you could try additional troubleshooting steps with backup options.
Moving the drive to another computer or a hard drive enclosure are some options.
There are steps that can be used to troubleshoot failed upgrades.
@zbook, in case you haven't read right back to the beginning of this thread here's the backstory in a nutshell.
The drive has already been in an enclosure connected to another PC. After a few false starts we got it to be recognised, but it had no partitions. Jumanji then stepped in and helped recover the partitions, after which the user files were backed up.
The drive is now back in the original laptop and back to its original 'booting' problem, which hopefully you'll be able to help fix.
Earlier in the thread steps were made that indicated the files sizes were of sufficient size to attempt a regback repair.
See post #101
Code:C:\>cd \windows\system32\config C:\Windows\System32\config>dir Volume in drive C is OS Volume Serial Number is 3E52-3D3B Directory of C:\Windows\System32\config 05/23/2018 12:26 PM <DIR> . 05/23/2018 12:26 PM <DIR> .. 05/23/2018 12:18 PM 524,288 BBI 05/23/2018 01:04 PM <DIR> bbimigrate 06/10/2018 10:29 AM 28,672 BCD-Template 06/09/2018 09:19 AM 33,554,432 COMPONENTS 05/23/2018 12:30 PM 524,288 DEFAULT 06/09/2018 07:13 AM 6,029,312 DRIVERS 04/11/2018 05:04 PM 8,192 ELAM 04/11/2018 07:38 PM <DIR> Journal 05/23/2018 12:05 PM <DIR> RegBack 05/23/2018 12:30 PM 28,672 SAM 05/23/2018 12:30 PM 57,344 SECURITY 06/09/2018 12:08 PM 78,381,056 SOFTWARE 06/08/2018 04:04 PM 17,301,504 SYSTEM 04/11/2018 07:38 PM <DIR> systemprofile 05/23/2018 12:07 PM <DIR> TxR 05/22/2018 04:43 PM 8,192 userdiff 11 File(s) 136,445,952 bytes 7 Dir(s) 321,097,179,136 bytes free
Let's see if this can fix the underlying problem.
1) boot to the Windows 10 iso
2) it may take 5 minutes displaying the windows icon
3) Use the default settings for language, time, currency, and keyboard
4) click next
5) In the left lower corner click Repair your computer
6) click troubleshooting
7) click startup repair (it is expected to fail)
8) click system restore (it is expected to fail)
9) click command prompt
You should see a pop up with title bar: Administrator: X:\windows\system32\cmd.exe
This is the registry backup method:
For each step you must see sizeable file sizes for this to work.
If you see zeros the method will fail.
The command: dir
will be used each step to make sure you are in the proper location and check the size of the files
10) type: C:
11) dir
12) type: D:
13) dir
Choose the C: or the D: drive to proceed. It should be the windows drive and not the USB drive.
14) type: bcdedit | find "osdevice"
This should display the location of the partition and in most cases is the location of the affected drive.
For this post I will use C: however you should pick the drive letter that you found that has the windows files on your computer.
The proper drive will display: perflogs, program files, program files (x86), users, windows, etc
15) type or copy and paste: cd \windows\system32\config
It should display: C:\windows\system32\config>
16) type: dir
It should display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk, journal, regback, systemprofile txr, etc.
All of the file sizes should be sizeable. If it displays zeros then abort.
Make a new directory and name it backup or something similar.
17) type: MD backup
Copy all of the files into this new directory.
18) type or copy and paste: copy *.* backup
It should now display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk indicating the files were copied.
Change the directory to regback
19) type: cd regback
It should now display: c:\windows\system32\config\regback>
20)type: dir
It should display: default, sam, security, software, system etc
All of these files must be sizeable. If it displays zeros then abort.
21) type or copy and paste: copy *.* ..
It should now display:
DEFAULT
Overwrite ..\default? (yes/no/all):
22) type: a
It should now display: sam, security, software, system and that the files were copied.
23) type: exit
24) click turn off your PC
Remove the USB flash drive if you had changed your boot order. Otherwise you can leave it and power on your computer.
Please use a camera or smart phone camera to take pictures and post images of the commands and results into the thread.
ZBook
If I boot it up right now, I get a 'please wait' message on blue screen for 15 minutes, then messages again on a blue screen, the messages are from the April Windows update, then I end up with the Desktop with one app; the Recycle Bin. The Desktop with one app has been described by lots of Avast users and has been related to April Windows update.
“In cooperation with Microsoft we have identified an element of the latest Windows 10 1803 update that is incompatible with the Avast Behavior Shield, causing the aforementioned update to fail in some instances''
If I follow the steps you kindly put up; there is a strong possibility that they might not work.