LOL.. looking at that old thread - I got my command syntax mixed up there as well...
What are the results of the sfc and dism commands?
We have to get those to complete without error before attempting fixing activation.
BTW I had to update LicensingDiag.ps1 as MS changed some stuff and the digital licence was not coming through on the report - you may wanna try running it again - it accesses the licence files and may help reset them in doing so.
I ran DISM /Online /Cleanup-Image /RestoreHealth. It came back with 21 errors, and the message "device not ready." It appears it is too large though to upload...
Here are a few excerpts:
2019-09-28 22:12:49, Warning DISM DISM Provider Store: PID=3316 TID=8056 Failed to load the provider: C:\WINDOWS\SYSTEM32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-09-28 22:12:50, Warning DISM DISM Provider Store: PID=3316 TID=8056 Failed to load the provider: C:\WINDOWS\SYSTEM32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
[3316] [0x8007007b] FIOReadFileIntoBuffer1381): Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.
[3316] [0xc142011c] UnmarshallImageHandleFromDirectory
[3316] [0xc142011c] WIMGetMountedImageHandle
2019-09-28 22:12:50, Info DISM DISM WIM Provider: PID=3316 TID=8056 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-09-28 22:12:50, Info DISM DISM VHD Provider: PID=3316 TID=8056 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-09-28 22:12:50, Info DISM DISM FFU Provider: PID=3316 TID=8056 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2019-09-28 22:12:50, Info DISM DISM Imaging Provider: PID=3316 TID=8056 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2019-09-28 22:12:50, Info DISM DISM VHD Provider: PID=3316 TID=8056 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-09-28 22:12:50, Info DISM DISM Imaging Provider: PID=3316 TID=8056 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[3316] [0x8007007b] FIOReadFileIntoBuffer
[3316] [0xc142011c] UnmarshallImageHandleFromDirectory
[3316] [0xc142011c] WIMGetMountedImageHandle
2019-09-28 22:12:53, Warning DISM DISM OS Provider: PID=11160 TID=3864 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2019-09-28 22:12:58, Warning DISM DISM Manager: PID=3316 TID=8056 Failed to delete the temporary provider store directory C:\WINDOWS\TEMP\6AF5961E-331D-473D-A8E0-1756BC800742. HR=0x80070005 - CDISMManager::CleanupImageSessionEntr
2019-09-29 11:16:07, Warning DISM DISM OS Provider: PID=14224 TID=6160 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2019-09-29 11:16:07, Warning DISM DISM Provider Store: PID=14224 TID=6160 Failed to load the provider: C:\Users\JONATH~1\AppData\Local\Temp\56964D7E-34A9-4C3F-9005-FA95CB5E6C57\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-09-29 11:16:08, Warning DISM DISM Provider Store: PID=14224 TID=7892 Failed to load the provider: C:\Users\JONATH~1\AppData\Local\Temp\56964D7E-34A9-4C3F-9005-FA95CB5E6C57\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-09-29 11:39:21, Error DISM DISM Package Manager: PID=14224 TID=7892 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070015)
2019-09-29 11:39:21, Error DISM DISM Package Manager: PID=14224 TID=7892 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070015)
2019-09-29 11:39:21, Error DISM DISM Package Manager: PID=14224 TID=7892 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070015)
2019-09-29 11:39:21, Info DISM DISM Package Manager: PID=14224 TID=7892 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2019-09-29 11:39:21, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070015
2019-09-29 11:39:27, Warning DISM DISM Manager: PID=13188 TID=14040 Failed to delete the temporary provider store directory C:\Users\JONATH~1\AppData\Local\Temp\56964D7E-34A9-4C3F-9005-FA95CB5E6C57. HR=0x80070020 - CDISMManager::CleanupImageSessionEntry
I looked at the CBS log, and say that Avast was still there...even though I uninstalled it...I just manually deleted it.
Still no further then I was yesterday...
- - - Updated - - -
Just posted excerpts from the Dism...I ran sfc /scannow, but it hung at the end, and I did not see any results.LOL.. looking at that old thread - I got my command syntax mixed up there as well...
What are the results of the sfc and dism commands?
We have to get those to complete without error before attempting fixing activation.
BTW I had to update LicensingDiag.ps1 as MS changed some stuff and the digital licence was not coming through on the report - you may wanna try running it again - it accesses the licence files and may help reset them in doing so.
Running the licensingDiag now...
- - - Updated - - -
tried the LicensingDiag...oh, I tried that way back on Friday...and I get the same error:
Something happened ;(
Die Benennung "C:\Users\Jonathan" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern enthalten), und wiederholen Sie den Vorgang.
Press any key to exit...
English:
Something happened;
The name "C: \ Users \ Jonathan" was not recognized as the name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if the path is correct (if included), and try again.
Press any key to exit ...
Wow.. that looks horrendous - I'm no expert at Dism but looks like a re-install is required.
Error 0x8007007e indicates some components were not installed properly - a repair install does not usually fix permissions errors but in this instance it seems more than that so worth a try (if you have not already)
https://www.tenforums.com/.../16397-repair-install-windows-10-place- upgrade.html
IIRC, last time I tried to do an "upgrade" from within Windows, the option to keep my settings and apps was greyed out...I will give it a shot and post the results.
Nice Texas accent on the video ;-D
- - - Updated - - -
The option to keep my personal data and apps is still greyed out...kind of hate to lose my apps and settings.
- - - Updated - - -
Making a tea and honey...I read the repair and install guide again, and am running the media creation tool again....
Good idea... make sure the version matches or supercedes the current install.. build, architecture, language... the works. If it doesn't you won't get to keep anything.
Also backup the crapola install with Macrium in case you may need to mount the backup to copy files to a clean install.
One thing I noticed using the media creation tool is that the suggested setting for language came up as English...I will be 2 .iso disks, one using German as the Language, the other with English. Funny, I am pretty sure I had a German version of 7 pro installed. I will keep you posted.
- - - Updated - - -
Well it took me ages to get the Win10-eng .iso disk burned; my burner would not write, so I put it on a stick and burned it to disk...2 times, so I copied it to here desktop, and burned it from there. The disk is in, and I have the proper allowance to keep my porgrams and settings...wish me luck, here goes-
- - - Updated - - -
Well it took me ages to get the Win10-eng .iso disk burned; my burner would not write, so I put it on a stick and burned it to disk...2 times, so I copied it to here desktop, and burned it from there. The disk is in, and I have the proper allowance to keep my porgrams and settings...wish me luck, here goes-
- - - Updated - - -
No joy, different error...0x8007025D-0x2000c, The installation failed in the SAFE_OS phase with and error during APPLY_IMAGE operation. Next thing is to try a clean install...
Not necessarily, it is possible to analyse the log files and troubleshoot a failed upgrade. Often is is possible to resolve the issues. See....
https://docs.microsoft.com/en-us/win...upgrade-errors
I do not know what happened to my last post but here goes again.
- I think the problem is with the first installation of Windows 7 Pro from a Dell OEM Disk when I built the system 7 years ago.
- When the Windows 10 Pro update came out, I updated using the German Version.
- When trying to get things in order, I messed with file permissions on my main account (also admin)
So it looks like I need to do the following:
- Save the Program folders to another drive, as well as Desktop and other personal settings
- Either do a clean install, not saving settings, and then reinstall the programs
- Format C: and do a clean install or lastly,
- Build a new system and start from scratch
I am leaning to #4. This system is over 7 years old, and maybe it is time to bite the bullet and build a new one. Jeepers though. 1.400€ ? I kind of had other plans with the funds.
I am really dependant on Email, Excel and the internet for my Auto Business here in Germany, and it is the end of the month and I need to write billings and offers for customers. (I am a Master Carpenter and Cabinet maker here in Germany, as well as working on my Meisterschein as an Auto Mechanic; the body says "no-more" to the carpentry work)
Oh, and you can find me on FB under Kriebel Kriebel to see the work I do on the old cars here in Germany. I am leaving tomorrow for North Holland (Island of Texel) to do some repairs on the house there. (Holiday?)
I looked for a donate button for the site, but did not find one...you all are doing great stuff here.
All the best,
Jonathan in Germany.
Quote
