'sfc /scannow' Exexcution Yields Response 'WRP cannot perform requested operatiom.'

Your right the quotes were missing.
Hope the following 'results.txt' file shows what your looking for.

HKEY_LOCAL_MACHINE\components\deriveddata\components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26
S256H REG_BINARY 1862F83919ECDFF7E643BFE701D9AEE1B33220C0D7416E020D32A0AB6B678D49
identity REG_BINARY 4E657446782D4153504E45545F57454241444D494E5F55534552532C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E332E393630302E31363338342C205075626C69634B6579546F6B656E3D623033663566376631316435306133612C2050726F636573736F724172636869746563747572653D783836
c!microsoft-w..-deployment_31bf3856ad364e35_6.3.9600.16384_03967f182a68b3d1 REG_BINARY
CF REG_DWORD 0x5
f!findusers.aspx REG_DWORD 0x21
f!manageusers.aspx REG_DWORD 0x21
f!edituser.aspx REG_DWORD 0x1
f!adduser.aspx REG_DWORD 0x21
 
Here's a new 'results.txt' file per your referral link in your post above.
To me it looks identical to the initial 'results.txt' file.


HKEY_LOCAL_MACHINE\components\deriveddata\components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26
S256H REG_BINARY 1862F83919ECDFF7E643BFE701D9AEE1B33220C0D7416E020D32A0AB6B678D49
identity REG_BINARY 4E657446782D4153504E45545F57454241444D494E5F55534552532C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E332E393630302E31363338342C205075626C69634B6579546F6B656E3D623033663566376631316435306133612C2050726F636573736F724172636869746563747572653D783836
c!microsoft-w..-deployment_31bf3856ad364e35_6.3.9600.16384_03967f182a68b3d1 REG_BINARY
CF REG_DWORD 0x5
f!findusers.aspx REG_DWORD 0x21
f!manageusers.aspx REG_DWORD 0x21
f!edituser.aspx REG_DWORD 0x1
f!adduser.aspx REG_DWORD 0x21
 
To double-check that I followed your instructions correctly, I re-performed
myjIXnC.png
SFCFix - Fix Time instructions in your post #49.
Your subsequent requested
EndqYRa.png
System File Checker (SFC) instructions in that same post were NOT re-performed.
Next I re-performed your instructions in your post #52.
The 'results.txt' obtained is shown just below.
HKEY_LOCAL_MACHINE\components\deriveddata\components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26
S256H REG_BINARY 1862F83919ECDFF7E643BFE701D9AEE1B33220C0D7416E020D32A0AB6B678D49
identity REG_BINARY 4E657446782D4153504E45545F57454241444D494E5F55534552532C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E332E393630302E31363338342C205075626C69634B6579546F6B656E3D623033663566376631316435306133612C2050726F636573736F724172636869746563747572653D783836
c!microsoft-w..-deployment_31bf3856ad364e35_6.3.9600.16384_03967f182a68b3d1 REG_BINARY
CF REG_DWORD 0x5
f!findusers.aspx REG_DWORD 0x21
f!manageusers.aspx REG_DWORD 0x21
f!edituser.aspx REG_DWORD 0x1
f!adduser.aspx REG_DWORD 0x21

This is identical to the 'results.txt' file I posted originally in my post #61.
You requested in your post #62 that I repeat the procedure, which I posted in post #63.

Since all 3 'results.txt' files are identical I think the instructions were followed correctly.

 
Alright it seems that the fix worked :) Now, we'll get a new CBS.log, and I'll be able to create the fix that we'll apply for all the remaining files.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
ALRIGHT!

I wasn't able to tell if the 'fix.reg' file code had repaired anything by looking at the 'results.txt' file (but I didn't know what I was supposed to be looking for to make this determination, either).

However I was looking at my latest 'cbs.txt' file last night and noticed a line stating a key had been successfully repaired. WooHoo!
And you confirmed this, this morning.

My latest 'cbs.txt' file is a compilation of the three last runs from 2015-08-23 10:36:41 to 2015-08-23 23:25:11.

See this 'cbs.txt' file in zip folder 'cbs' at OneDrive link https://onedrive.live.com/redir?res...05&authkey=!AFq3SFu0JAcFt5c&ithint=folder,zip.

I know you can't possibly have the time to explain what your doing to Sysnative members who are interested in following how you make their repairs.
There just isn't enough time in the day to analyze, implement the repairs and explain what your doing too (nevertheless holding down a fulltime job also).
If a member is interested enough though, they can learn some of what's going on by studying the sequence of your repair of their problem.

Again know that we're grateful that people like you and other Sysnative analysts are willing and able to help those of us who have backed ourselves in a corner and desperately need to avoid a system reinstall because of a minor Windows system error.
 
After looking at your CBS.log, it seems that the fix didn't work. The targetted value in the Registry was indeed modified so it holds the right data, but the error it was supposed to fix still appears in the log. I'm currently consulting with my teacher regarding our next course of action.
 
Thanks for your update.

To keep Windows Update from interfering and continually trying to install updates, I've have had (for some time now) Windows Updates completely shutdown.
Would this action on my part keep the registry key repair from actually be achieved even though you say the key contains the correct data?
This is just a thought, since it's a Windows Update problem we're trying to fix.
When Windows Update was enabled it reports many updates need to downloaded and installed (since I'm way behind in keeping them up-to-date).
 
It's okay to disable the Windows Update service for the time being. If we need it again, I'll let you know :)
 
Boo, do you happen do have your Windows installation media (CD, DVD or USB)? Reason being that if you do, we could do a repair install of your system instead. It would be much faster considering the size of the fix I would have to produce (over 175 Registry entries to search and enter manually). By the time I'm done, you could be back up and running already.
 
Here's the last requested 'SFCFix.txt' file (if it would help I can run a new one).
See comments below the file.

XXXXXXXXXX
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-08-23 16:56:56.245
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\Bernard Spaulding\Desktop\SFCFixScript.txt [3]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-aspnet_webadmin_users_b03f5f7f11d50a3a_6.3.9600.16384_none_4cc4ad18b1f53a26.
RegistryScript:: directive failed to complete successfully.


Failed to process all directives successfully.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 19 datablocks.
Finish time: 2015-08-23 16:56:58.155
Script hash: rkCev2bdQT3IOQZ3d7uakjaqsm0s5mTW4zHJ9fnh+D8=
----------------------EOF-----------------------

XXXXXXXXXX

I was wondering about that.
That being implementing the repair once the problem has been identified.
I suspected that each registry key requiring repair had to be coded individually and manually by you.
Which can be time consuming if there numerous keys to repair (you stated 175 or so for my case).
I suppose maybe code could be created to automate the repair process, but that would probably take more time than doing the repair manually.

Once you have successfully repaired the test registry key, maybe you could instruct me as to the procedure to correct the remaining 174 or so keys (as I have the time to do this).
Again then this may be out of the question if the process is not repetitive (meaning I'd only have to enter specific registry key code into your created script).
Then again this repair process may be much more involved than I realize and not a viable option.

My system is a Dell Inspiron 13-7347 '2-in-1' laptop.
It was shipped without installation media (as most systems are today that don't have an optical drive).
I ordered and have on hand a USB flash drive that will restore the system to factory OEM software (as out of box new condition).
This DOES NOT retain my current data files nor any of the applications I've installed since beginning use of the system.

The hard drive does have a hidden partition that will restore, repair, or reset using Dell's Backup and Recovery software.
But because of the current Windows software problem with this computer Dell Backup and Recovery can't successfully execute any of these 3 functions.

If the USB flash drive has the registry key file data (which I think it most certainly does) and this can be accessed to repair (replace) the corrupt (damaged) keys, then this is probably the way to go.

I've been thinking about this method for some time now, but I don't know how to go about it to ensure that I retain (don't lose) user data files and applications in the process.

What do you think is the best option?
 
You are running Windows 8.1 x64, and I happen to have the .iso for it. All you would need to do is to download the .iso and mount it (right-click on it and select Mount), then access it like you access any CD or DVD on your computer and launch the setup.exe. From there, when it asks you what kind of installation you want, you would pick the first one Upgrade and this would run a repair install. Your programs and files are preserved in the process. It's still recommended to back them up just in case (your files).

The best option (and the fastest one) would be a repair install. Also, the fix isn't something really I can teach you since there's too many things to take into consideration and without adequate training it won't be possible sadly.

Here's a little read about the repair install process under Windows 8.1.

https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html

This article shows the process using a bootable USB, but you don't really need one.
 
I take from your last post that doing a repair install is your recommendation.

I certainly don't want to burden you with a laborious and lengthy registry repair coding task, especially since you say it's impractical for me to do the majority of the work due to the complexity involved.

You say you can provide a Windows 8.1 64 bit '.iso' for download.

Is it a generic operating system download that will accept my system's licensed 25 character software registration code?

My system is running Windows 8.1 64 bit (Update 1).

Is your '.iso' Windows 8.1 64 bit (Update 1)?

I appreciate the enclosed link explaining how to perform an operating system repair install.

I will make a hardcopy for reference to follow steps to ensure a successful repair install.

Also I'll make a backup of my system just in case the repair install goes awry.

I've briefly reviewed the link you provided about the repair install procedure.

Does it cover making a backup before doing a repair install?

If not, can you provide a link to a good backup procedure?

This is all new territory for me and I want to make sure I do it right (correctly).

If you'll provide the '.iso' download I'll get started.

Please make any other suggestions considering what I've written above.

And I'll be sure to consult with you any problems encountered and keep you posted on my progress.
 
You say you can provide a Windows 8.1 64 bit '.iso' for download.
Is it a generic operating system download that will accept my system's licensed 25 character software registration code?
My system is running Windows 8.1 64 bit (Update 1).
Is your '.iso' Windows 8.1 64 bit (Update 1)?
Click to expand...

Do you have an OEM copy of Windows 8.1, or a retail? Basically, did you buy and install Windows 8.1 yourself, or did it come with your laptop/computer?

Does it cover making a backup before doing a repair install?
If not, can you provide a link to a good backup procedure?
This is all new territory for me and I want to make sure I do it right (correctly).
Click to expand...

It doesn't no. Basically, you want to back up all the folders where you have your personal files. Usually, they are:
Code: 
C:\Users\$USERNAME\Desktop
C:\Users\$USERNAME\Documents
C:\Users\$USERNAME\Music
C:\Users\$USERNAME\Pictures
C:\Users\$USERNAME\Videos
C:\Users\$USERNAME\[Any other folders you personally created in your userprofile directory]
C:\[Any other folders you personally created at the root of your C: drive]
 
My system is a Dell Inspiron 13-7347 '2-in-1' laptop.

It was shipped without installation media (as most systems are today that don't have an optical drive).

I ordered and have on hand a USB flash drive that will restore the system to factory OEM software (as out of box new condition).

This DOES NOT retain my current data files nor any of the applications I've installed since beginning use of the system.

It wipes the system clean and restores it back to what software was OEM installed on it when new out-of-the-box.

User installed data and user installed apps are lost.

This is what I'm trying to avoid by working with you to get my registry restored.

I do not have separate physical Microsoft Windows 8.1 64 bit (update 1) installation media (which I'm legally entitled to).

Basically I do have it on my system's hard drive in a hidden recovery partition called Dell System and Recovery software.

The key I have for recovering my system is tied to Dell System and Recovery and for this and only this system (as the OEM software registration key is somehow associated with the motherboard ID).

OEM software registration keys and retail Microsoft Windows software registration keys are different from each other and hence are NOT (to my understanding) interchangeable.

The problem being that because of my Windows registry corruption Dell System and Recovery is unable to recover my system.

It's like being caught between a rock and a hard place, up the creek without a paddle, or catch-22.

It seems there should be a way for legitimate (license paid) users to get retail Windows 8.1 64 bit (Update 1) installation media (either physical or download).

Do you have any thoughts on how to proceed?
 
Well at this point it seems like we don't have a lot of options:
  • Either I work on a fix for your system (which could take up to a week);
  • Either you reinstall Windows from scratch using the USB you have;
  • Either you can get a hold of a Windows 8.1 Update 1 x64 .iso from which you can run a Repair Install;
The choice is up to you. The easiest of course is the repair install method, but without an .iso, we cannot do it.
 
READ ALL. THERE IS A POST IN THIS THREAD THAT MAY HAVE GONE UNNOTICED AND MAY POINT TO A POSSIBLE PROBLEM SOLUTION.



The 1st option puts all the work on you repair coding 175+ registry keys (per your post #71).

I wouldn't expect you to undertake this task unless you are reasonably sure that it will solve my registry corruption problem.

You wouldn't want the time and effort to be for naught.

This option will only be used if your willing and only if I can't obtain an '.iso' which will permit a repair install of the operating system.

A week's time for you to prepare the repair code is a short time considering I've had this SFC issue since April.

The 2nd option of succumbing to a wipe and OS reinstall and then having to install saved user data and reinstall user installed apps isn't an option.

The 3rd option of a repair install is the option of choice.

This option requires an appropriate '.iso' file to effect an operating system repair.

Since I don't have physical installation media, please look at the '.iso' downloads in the following link to see if they will suffice to effect the OS repair.

http://dellwindowsreinstallationguide.com/download-windows-8-1-retail-and-oem-iso/

The two downloads (Windows 8.1 Retail .iso & Windows 8.1 OEM .iso) are at the end of part 2.



The other item I wanted you to see again is in post #31.

Note the three items in blue at the bottom of the 'Search.txt' file pertaining to KB3022345 causing corrupt files.

I didn't see the 3 items in the 'Search' text report, and this is brought to your attention just in case you didn't.

Recall that KB3022345 couldn't be uninstalled with dialog titled 'Windows Standalone Installer' Error: 0x800703f1 - The configuration registry database is corrupt.
 
If I read it correctly, this article points to the Windows 8.1 Media Creation Tool that can be used to download a Windows 8.1 Update 1 .iso that you can use to do a repair install. However, this tool only accepts retail product keys, and not OEM like you have. Microsoft stance on this is that if you have an OEM copy of Windows, you should be getting the installation media from your computer's manufacturer, and not them. You can try to input your product key and see if it goes through, but I doubt.
 
Please read post #79 just above and this post below all the way through to the end.

Thanks.
----------



The 'Dell Windows Reinstallation Guide' referenced in the last two posts (#78 & #79) is apparently a clean reinstall of 'Windows 8.1 Update 1' for either retail or OEM system 'Windows 8/8.1' installs.

The 'Media 8.1 Creation Tool' creates a 'Windows 8.1 Update 1' ISO file which can be saved and then used to make a bootable USB for reinstalling 'Windows 8.1 Update 1'.

Following instructions in the guide a bootable USB was created successfully.

When the bootable USB 'setup.exe' file is executed, clean installation of 'Windows 8.1 Update 1' proceeds.

Early in the setup after making sure system installation requirements are met, it requests permission to uninstall user installed apps that were not part of the original (retail or OEM) Windows operating system installation.

Hence why I take this to be a CLEAN install and not a REPAIR install.

This is reinforced in the sentence just above Part 7 of the guide which states " If you had no problems determining your Edition, making the .iso and are ready to clean install see Windows 8.1 Installation.".

A repair (non-destructive) install such that data files and apps installed by the user (after the system was first put into service) is required.

Thus the ISO available from the 'Dell Windows Reinstallation Guide' isn't a solution since it is not a repair installation.

The Dell backup media for my Dell Inspiron '2-in-1' laptop (with Dell OEM installed Microsoft 'Windows 8.1 Update 1' OS) is available from Dell at no cost if the system is still in warranty.

I have this backup USB media on hand, however when used it is also a clean reinstall, restoring the system software back to new out-of-the-box factory state.

So again this is not a repair reinstall solution that leaves user installed data and apps undisturbed.

The 'Dell Backup and Recovery' software (that is included as part of my Dell OEM installed operating system) is on a hidden partition.

When system recovery is called to do a task it opens and the operations available to the user (me) from the troubleshooting screen are

1. Refresh your PC
2. Reset your PC
3. Dell Backup and Recovery
4. Advanced Options

Options 1 and 2 are not viable solutions as user installed apps are lost.
Option 3 would normally be the option of choice, but because of a configuration database corruption it fails to complete.
Option 4 has been somewhat explored, but a solution hasn't been found yet.

As I stated in post #76, there seems no place to turn as an obstacle crops up no matter which solution direction is taken.

Since my system has an OEM operating system installed, I'm not sure even if I had a same edition retail Microsoft 'Windows 8.1 Update 1' (64 bit) operating system, that I would be able to use it as a repair installation to repair my corrupt configuration database.

Dell as well as other manufacturers use Microsoft operating system deployment software to install operating systems on end user systems.

I doubt that a 'Microsoft 8.1 - Full Version' retail edition would be able to repair my Dell OEM installed operating system.

Your thoughts?

Back in your post #73 you state you have a 'Windows 8.1 x64' ISO.

If I acquire (through legitimate means of course) that (identical, same) ISO, will it be capable of repairing my Dell OEM 'Windows 8.1 x64' installed operating system?

I'm assuming the ISO you have is one you created from a 'Windows 8.1 x64' full version edition and that it has repair capability built in.

There is available Windows 8.1 64 bit software DVDs (ie - http://www.amazon.com/gp/product/B00S8TYVCI/ref=s9_simh_gw_p65_d0_i1?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=0JMFHEESV8ZH21P22VT6&pf_rd_t=36701&pf_rd_p=2091268722&pf_rd_i=desktop).

I don't understand the legitimacy of this software.

If you read the description of the product carefully you'll see two caveats (1. a missing or compressed repair BOOTMGR and 2. a missing NTLDR).

Maybe by removing these 2 utilities DirectSystems can offer for sale Microsoft operating system software legitimately at much reduced cost.

I'm not against obtaining this or a similar offer if it will serve the purpose of restoring my OEM operating system software installation.

Especially if thwarts having to do a manual repair saving time and effort.

Can you shed any light on whether this is a viable alternative?

Just don't want to make this expenditure if it won't do the job.

Those who purchase computers with OEM installed operating systems should have legitimate access to the equivalent full version Microsoft operating system directly from Microsoft at no cost without any hassle.

Especially since the operating software is included in the purchase cost of the computer.

If that software is available I've yet to find a source for it.

It's certainly not readily available from the Internet or directly from Microsoft.

At least from any of the locations searched thus far.

Possibly someone reading this post knows of a source and would post where a legitimate full version of 'Windows 8.1 Update 1 x64' can be located for those users that have a registered OEM or Retail key.


----------
AURA,

In the mean time, it seems manually repairing the corrupted configuration database to avoid a clean reinstall of 'Windows 8.1 Update 1' with the attendant chore of reinstalling all saved user data and user installed apps may be my only choice.

Back in post #67 (please refer to) you state the repair fix for the one registry key you were working on didn't take.

However you also said the targeted registry key value was modified and holds the correct data, but the error still exists in the 'cbs' log.

Would you mind tackling this again (at least for this one test key) to see if you can get this test key to report its been fixed in the 'cbs' log?

Your comment on any of the above subject matter in this post is welcome.

Thanks.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top