New
#11
Thank you for System Spec Update.
Man, why such a hassle to get data and logs.
We can't help you without diagnostics, usually.
Bill
Thank you for System Spec Update.
Man, why such a hassle to get data and logs.
We can't help you without diagnostics, usually.
Bill
Cittizin7,
As the CBS.log indicated, here is the relevant part of the WinUpdate.log
Fix is way more difficult than Repair Install, here's the Details from my OneDriveCode:2019-09-13 03:37:25:320 2696 d30 WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable' 2019-09-13 03:37:25:320 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea' 2019-09-13 03:37:25:320 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize' 2019-09-13 03:37:25:321 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea' 2019-09-13 03:37:25:321 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance' 2019-09-13 03:37:25:325 2696 d30 WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable' 2019-09-13 03:37:25:325 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea' 2019-09-13 03:37:25:325 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize' 2019-09-13 03:37:25:325 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea' 2019-09-13 03:37:25:325 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance' 2019-09-13 03:37:26:349 2696 d30 WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable' 2019-09-13 03:37:28:309 2696 d30 WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable' 2019-09-13 03:37:28:310 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea' 2019-09-13 03:37:28:310 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize' 2019-09-13 03:37:28:310 2696 d30 WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea' 2019-09-13 03:37:28:310 2696 d30 WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance' 2019-09-13
Repair Install Instructions.docxCode:Line 7843: 2019-10-02 18:00:00:161 492 860 AU WARNING: BeginInteractiveInstall failed, error = 0x8024000C
Bill
If you need help with that, yep.
Thanks to SNICK & PAUL BLACK for your assistance!
I really appreciate all the tools to prep for a Startup Repair, or a Repair Install - Yeah, I was fine with that term too, then they changed it!
Anyway, marking this thread as, SOLVED, though I have yet to do the Repair. I think I'll manage, but thanks for the offer to help with this too.
Also, intend on doing some searching on the data you provided where things went wrong. Repair Install can "fix" a lot of problems, but, though I am not an IT professional (self-taught), I like to try and learn something new if I can. If you are so inclined I think I have enough experience to follow an explanation or any information that would make my searching more productive would be appreciated.
My apologies to SNICK for my oversight on providing my system specs up front.
Thanks again!
Cittizen7
Hi Cittizin7,
You know where we are!
Repair Install - Overview
A repair install differs from a clean install in the fact that it ONLY replaces the corrupted OS with a new fresh copy. This means that ALL your User Accounts, Folders, Files, Documents, Pictures, Music, Videos, Data Files, Icons, and any installed programs are left intact. It does however, delete ALL the Window updates, and could possibly affect, sounds, services, visual effect settings and device drivers by re-setting them to default [unusual though]. You cannot do a repair install at boot, in Safe Mode, using a system repair disk, or using an integrated Windows update disk. Basically, this process can ONLY be performed from within the LIVE OS.
The easiest way to perform a Repair Install is . . .
[1] Disconnect any external HDD's.
[2] Create a folder on the Desktop, something like Clean_Inst.
[3] Copy the ISO [DVD or USB files] into it.
[4] Unzip the ISO using something like 7-Zip. Click here => 7-Zip.
[5] Find and double-click the Setup.exe file [follow the prompts].
[6] When you get to the installation screen, select In Place Upgrade [Repair Install].
There are obviously tasks that need to be performed before you start a Repair Install, but I presume from what you have said that you know this anyway. Don't forget to have you Product Key available!
I hope this helps!
Last edited by Paul Black; 16 Oct 2019 at 02:59.
Startup Repair and Repair Install are not the same or similar.
The only part similar is the work repair.
Well, I can explain pretty much everything you need to know. Most of which you will not find on the internet in regards to Windows Update. But, as you wish, proceed on your own.
However, if you wish to continue with our assistance, leave the thread open or, in the alternative, start a new one.
Most individuals don't understand Windows Update. It can be broken and not appear so until something in the link chain that you see quits functioning as it should or all together.
What I do is get you so that Windows 7 works as it should again, In-Place Upgrade or Repair Install, one in the same.
or
Upgrade to Windows 10 Still Free
I like free.
Bill
Ok, so I guess I did mark the thread SOLVED prematurely in that I probably should have help through the Repair Install process since the last time I did it was with windows 2k! And because I think I'm seeing some difference of method:
Are all 3 Servicing stack update for Windows needed for Fresh install
For personal reasons, this will probably take me more time than most to do, which is why I searched the forum and was thinking of using the info from the above link, but if you don't mind the time frame, then i would very much appreciate a walk-through.
Let me know for sure if I should open a new thread.
Also, I realized by your reply that I don't know as much as I thought I did about a Repair Install, so thanks for the education/clarifications. In my last post, I was wondering more about the log data you posted. What internals of windows other than WU update were involved? Did I do somthing wrong during the Clean install? Just thought it would be interesting to learn a little about just what the culprit was.
Thanks!
I have your link from previous post, so I will review that and get started on what I know. Just scanning the following...
Repair Windows Without Reformatting.docx - Microsoft Word Online
Oh, ok, this HELPS!:
Repair Install
I have experience with using Rufus, though I have my original DVD and my drive works.
I haven't used keyfinder or DISM++ yet. And see disc cleanup very low disk which I've never used.
I'll get back to you when I fully read over all this and let you know where I am.
Thanks!
Cittizin7 better to work with Windows 7 x64 ISO with SP1
Repair Install Better Instructions With Hypertext Links & Video
I can TeamViewer: The Remote Desktop Software with you if you wish
Ok, this is getting overly confusing already.
If I don't want to do the repair on-the-fly from my DVD, Can't I just drag and drop the files and folders from my DVD to my desktop and use setup that way without downloading an iso from the microsoft links in your tutorial? If I'm just running from the desktop, I don't need anything to be bootable, right? How will setup.exe know the root is my desktop?
If I DL using the windows dl tool thing do I select from the OEM set of versions? I ask because I have a cyberpower build and the alternative "Download from the new Recovery Center" option at heidoc says I need to contact my pc mfg. due to my license. So I assume it's considered an OEM license/product, right? I've always gotten this confused!
I would still like to know if I can DL the ISO using the windows-iso downloader in case I ever loose my DVD. What item in the drop down menu do I choose? OEM ...?