Main Forum > General Computer Support

problem with Win 10 upgrade from Win 7 64-bit

<< < (6/8) > >>

TelKen:
No logs in $windows. bt folder or sub-folders.

TelKen:
Re the edit to registry, I checked the registry and it already had that entry!

TelKen:
Result from tonight's Windows Repair Scan->

Scanning Windows Packages Files.
Started at (12/08/2015 23:25:11)

These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 22)
C:\Windows\servicing\Packages\Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Branding-Professional-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Branding-Ultimate-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Client-Wired-Network-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-CodecPack-Basic-Package-wrapper~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-IE-Troubleshooters-Package-wrapper~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package-wrapper~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-RemoteFX-RemoteClient-Setup-LanguagePack~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-Security-SPP-Component-SKU-Ultimate-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-CommandLineTools-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-MiscRedirection-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-Publishing-WMIProvider-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-UsbRedirector-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-TerminalServices-WMIProvider-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-UltimateEdition~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
C:\Windows\servicing\Packages\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514.mum

22 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.

TelKen:
OK I have cured my updating problems, repaired the corrupt Package Files, Win 10 installed and now in use.

There is one easy cure for Win 7 to Win 10, use your Win 7 install DVD and do repair. I had forgotten this, when my son a computer geek said Dad surely you can do a repair, reawakened my memory cells. All is now fine!

Shane:

--- Quote ---OK Shane I'll check that out. Meantime I found this on the internet after doing some searching, apparently it came from Microsoft.

“Locate the registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
It should exist, but if not, create it.
Create a new DWORD (32-bit) Value with Name = “AllowOSUpgrade” (without the quotes), and set the Value = 0x00000001.” (Source: microsoft)
--- End quote ---

Any chance you have a link of where you found that info?

Shane

Navigation

[0] Message Index

[#] Next page

[*] Previous page