A problem with updating on dev releases
corilani opened this issue · 12 comments
I tried to update from 22000.194 release to 22471.1000 using ISO. Tried manualy, by mounting and executing, tried via this tool, both gave the same result: preparing window is finishing up, blue screen of setup is starting, 0% of setup is showing for 5-10 seconds, after this getting error message "Windows 11 installation is failed"
My device is far from supported, tried editing registry by some manuals, but no positive result from them
Is this error because of insider channel isn't supported by device? And is there any chance to bypass this with this tool?
Thanks
One question I have is whether the tool bypasses the NTFS version conversion.
For instance when Windows 10 first beta came out in 2014, it converted to NTFS version 3.1 with LFS version 2.0 as revealed by Admin command : fsutil fsinfo ntfsInfo C: (or other boot drive letter)
Otherwise I am not sure whether the upgrade picks up the max path length in prior registry, so if you have some system files with path 941 characters in length as to whether the NTFS integrity routine would interrupt the upgrade. I am in no rush to upgrade and rather trying to verify all the critical core changes that are not publicized at this point, so I could safely take the jump.
Found a resolve. Firstly, you need to enable windows insider programm, by editing registry, or more automaticly, more info on: https://winaero.com/how-to-enable-windows-11-dev-channel-on-unsupported-device/ . I tried both methods, at the beggining edited registry, after that run cmd, selected Dev (1). Then run ISO via tool (Windows11Upgrade). Worked for me (Updated from 22000.258 to 22478.1012)
Hi,
i will explore it more and implement it in the next version so its done automatically.
coofcookie
Hello -
Could you share what NTFS & LFS version you have in Windows 11 ?
(Admin command line if C: is boot drive : fsutil fsinfo ntfsInfo C: )
Also note that the ones who enabled NTFS long paths (e.g. 32767 characters) might have issues if they wanted to go back to a Windows version before 1607, such as 1511 or Windows 8 or 7.
Hence whoever wanted to go back to prior versions after August 2, 2016 might not have been able to recover files with path length over 255 characters unless they renamed them beforehand.
Cheers,
Christopher
Hello - Could you share what NTFS & LFS version you have in Windows 11 ? (Admin command line if C: is boot drive : fsutil fsinfo ntfsInfo C: )
Also note that the ones who enabled NTFS long paths (e.g. 32767 characters) might have issues if they wanted to go back to a Windows version before 1607, such as 1511 or Windows 8 or 7. Hence whoever wanted to go back to prior versions after August 2, 2016 might not have been able to recover files with path length over 255 characters unless they renamed them beforehand. Cheers, Christopher
NTFS Version: 3.1
LFS Version: 2.0
If it's matters, previously I was using windows 10 (clean install) and after some time upgraded to windows 11
So that's not an issue, since it's the same as Windows 10. I doubt Microsoft will change NTFS or LFS versions within the life of Windows 11.
Thanks.
Piggy backing off of this - when using this tool to upgrade 22471 to 22523, Windows now says it cannot install because my PC is missing secure boot and TPM 2.0. It is, but shouldn't those checks be bypassed?
Me too.. cant update from 22504 to 22518 (iso pulled from upp dump...hope thats not the issue)
Hey, i know a fix with this you can use the iso i can give you an dev iso.
How to do it:
Replace the original install.wim from the original windows 11 (not insider) with the DEV iso.
Hey, i know a fix with this you can use the iso i can give you an dev iso.
How to do it: Replace the original install.wim from the original windows 11 (not insider) with the DEV iso.
I tried putting the install.wim from the latest insider dev iso into a non-insider iso (from microsoft.com). Still nothing .. now it just gets stuck on "instaling, please wait" cpu util goes down to 0 and nothing happens .. ram usage at 45mb
Hey, i know a fix with this you can use the iso i can give you an dev iso.
How to do it: Replace the original install.wim from the original windows 11 (not insider) with the DEV iso.
I have tried this with a few different ISO transplants, no luck.
**smurfhunter ** commented on 24 Dec 2021
This is because Microsoft changed setup code and now it checks if appraiseres.dll is present. If it is not, than it will not upgrade. To upgrade you need a compatible PC and change the "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\vdsldr.exe\Debugger" value to the "c:\windows\system32\11\vd.exe" (without quotes). This will revert the changes from the script present inside the app and you will be able to upgrade to the insider build on COMPATIBLE PCs only. Maybe there is a way to bypass, idk, but at least now this is the only way.