New
#10
On a vm I clean installed with 263 slipstreamed into the wim and couldn't install the 264 update.
On a vm I clean installed with 263 slipstreamed into the wim and couldn't install the 264 update.
Indeed, I misunderstood your issue in the other forum, this update fails on systems that have .263 already installed. They are the same KB number and possibly conflicting, and there could be actually very little difference between them.
BTW, my system froze the other day when using edge browser, on .263, so i rebooted and now using only the dev edition of chredge, for now it is fine. some people say the original edge was removed from their taskbar if they had dev installed and updated to .263.
Apparently some of the novelties of version 20H1 are already being tested in the Release Preview ring, these changes made in the Windows Ink Workspace has been back-ported to version 1903 with this CU:
Windows Ink Workspace in build 18362.264.
It seems like if you ran the dism /online /cleanup-image command after installing the previous 263 update it breaks it so that you can't install 264.
Hi there
Updated via UUPDUMP from 263 seems to be the best way to manage these updates IMO. OK It isn't testing the officia l WU but if you want the releases it's the best way to do it. Backup existing systems first of course evenn though with the windows.old you can revert -- I prefer my own backups though.
Cheers
jimbo