New
#141
Guys,
Thank you for your help.
This is a LTSB 10240 from regular hash-checked ISO.
I cannot install the November 10586 fix in LTSB.
Guys,
Thank you for your help.
This is a LTSB 10240 from regular hash-checked ISO.
I cannot install the November 10586 fix in LTSB.
I would assume the Pro and Enterprise PSD1 files are the same...
That zip file - was taken from an extract 10240 Pro install.wim
it is the C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SmbShare
folder and contains the file - your SFC is reporting as corrupt
the file that is corrupt is referenced by the 3 language packs
you can also refer to this topic, post 3 - Image health - option 3 >
Windows 10 Recovery Tools - Bootable Rescue Disk
Hmmmm ...Yup, LTSB cannot be upgraded ... but can't it be repaired via DISM? (as in from source)
Just wanna know as I have not used it and wonder if WU ignores it (froma restorehealth point of view)
Dism should work the same.. If /restorehealth does not do it,
/restorehealth /source should as it is a common windows setup file
Now I have the original SmbShare folder from ISO saved in a USB pendrive but see the screenshot.
Still I don't understand how to follow these instructions at post #3 with my pendrive:
"Option 3 RestoreHealth /source
Note: Dism uses the component store as it's main source for Image Repair, and windows updates are placed in the component store, so best to try to use current component store for RestoreHealth,
before selecting Option 3 and redirecting the repair source, to the windows setup media.."
From the read me:
>>Step 2: Right-Click IMAGE_HEALTH.CMD > Select Properties > Select Unblock
'Unblock'? do you mean de-select Read-only?
Attachment 52672From the read me:
>> Step 2: Right-Click IMAGE_HEALTH.CMD > Select Properties > Select Unblock
'Unblock'? do you mean de-select Read-only?
select unblock
if it does not state as above - just right-click image_health.cmd and choose run as administrator