Okay guys I have to go in a couple if minutes Those of you with custom resolutions! That's not the issue. It's that you're output path or img path is incorrect... @alexwilson will be back soon to help. Pm me and I'll get back with you. It's easier for me to narrow down the problem. I'll help you in the next couple of hours .. So better to pM me and I'll get back with you in a couple of hours BTW: Send me your edited ps1 file when you pm me so I can inspect it... Thanks
edit it and remove the if statement then it will run. i had that problem on 10159. not related. I got it to work with a normal resolution on 10159 so it appears it was the custom resolution on the other laptop
Yea, after removing: Code: if ((Get-FileHash -Path $priPath -Algorithm MD5).Hash -ne "9ECEE07E8E4E8011C02EE6AA8015B0D2") { throw "Not compatible with this PRI file." } Everything is working OK, tnx guys
Sorry for so many posts but i fixed it on the computer with 1280x800. what i did was go through all the resolutions replacing every number and found out that the 1920x1200 (option 5) was the one that it was using. so if you have 1280x800 it appears to use that resolution instead.
It doesn't work that way. You need to find the resolution in the list closest to the one you are using and then set $blobToReplace to the corresponding blob number. We don't know the exact algorithm by which Windows determines the best matching resolution so you may need to try different ones. No need for elevation if you set the output path to a user directory, e.g. desktop. You only need admin rights for replacing the PRI file afterwards. Those that get an MD5 error probably use a different build than I used (I was on 10166 x64). For other builds/editions it may still work (if the file structure hasn't changed considerably) or it may not. I'll try to have more robust steps on how to edit the pri file of any build sometime soon.
curious if sfc /scannow will bother with this or if it will effect Windows Update somehow. Would be way cool to see if someone can simplify this into an app, maybe another winaero application in the making?
SFC won't be affected by this, it only checks executables. But updates to new builds will overwrite the PRI file.
Thanks, so it isn't a system file changing hack (so to speak) that effects the "system" anyway. Should be safe enough that once updates are in place it can be re-applied then. This is such a big thing to a lot of people, I am very surprised MS didnt allow changing of the screen from all the insider comments.
Someone really need to work out the kinks and do a GUI version, it'll come soon enough from someone I Guess That said, thank you labvxe and alexwilson
That solved my problem. Before I was trying to make a custom resolution of 1920x1080 and that didn't work. Setting the blob to 5 makes it work now, thanks!
yeah perhaps just make it replace every resolution for simplicity, automatically back up and replace the old .pri and load an image. the script could probably be modified to do most of that. EDIT: been doing some fiddling and besides making the script automated as above minus the image path. If you dont specify a valid image it will convert the login screen back to the old solid colour.
I got word a little while ago from Gabe Aul that we couldn't change the login wallpaper. Just submit the feedback to stupid feedback app. But we did it! It looks like we won't get the option to change the login wallpaper from Microsoft Okay...NEXT UP. Is anybody willing to participate to make a GUI (graphical program) so we can change wallpaper...
sorry i couldnt follow the progress the last few days looks like you did it again, thanks for the hard work this method adds a specified image to the pri right? does it change other files? would it be possible to make a pri that looks for (or links to) an image outside the pri file? that would make it easier to change the background image by just replacing it as long as it has the right file name can someone upload a/the modified file/s without a valid image? (so that it goes back to simple color) maybe for 10176 and 10240