Here we go again.. Bulls**t. That file is from a CBS package. Not from the installer. Bulls**t, because that file is also not taken from the installer. No, you cannot discuss the content, because you clearly don't understand it. You cannot know the consequences because you have no idea what you're talking about. That file is only used by appraiser.dll and its CSP equivalent, nothing else. Those are literally useless as for "how the system was installed". PS: The Server method does not remove appraiserres
When you open those files and read in them what it says then maybe you understand. Don't even answer before that, because by attacking without arguments you can impress beginners not me, so stop, if you want to talk constructively OK, if you don't **ck off. PS. you probably have a hard time reading those files, you deleted one and the other is nuked in all cases as you say. You will have to reinstall Windows my way to view and edit them. So when you install it on VHD you don't need anything, and nothing touched. And you can write under the right nick, not this fake, these simultaneous attacks of the same person by two or three nicknames to make his story seem more credible, stronger support, forget it, I don't answer anymore
No, I didn't say that. No, they aren't deleted. I don't even need to look at them. You're the one who doesn't provide any proof for your endless bulls**t. Random hex dumps won't impress anyone and you're not fooling anyone here. appraiser.dll and Appraiser_Data.ini are in install.wim, the installer doesn't modify them.. The installer doesn't even use appraiser in any way, shape or form.. Here's proof both files are in install.wim: And then there's Appraiser_Data.ini in one test case: And as you can plainly see, it's from CBS:
Dear God where I waste my time? The people who created these monsters and this three iso sandwich monsters, they say this three-bit file is dangerous and it should come with big fat warnings and guides on how to overcome it. And expect me to expand the story to talk to them, my dear God!
Half of the things you do in your Unattend don't have any effect, as others and I have shown you before Your appraiserres "patch" doesn't work for unsupported CPUs Your appraiserres "patch" doesn't work for unsupported amounts of RAM You consistently confuse upgrades with clean installs and even wanted to automatically format people's PCs with this stupid Unattend You pretend this method is even comparable to others, when it's use is severely limited You haven't actually proven any claims you've made so far All other methods you mentioned in that post actually fully work. Yours doesn't. We don't "expect" anything from you. We're just telling you your s**t barely works and you're almost always wrong. You waste your time right here in this thread you created. You were proven wrong as many times as you have posted here Edit: Please think before you type and don't edit posts every 30 seconds for the next few days after you make it. Your childish insults and redaction of severe stupidity haven't gone unnoticed.
You all wrong. At the end we all try to find a damn solution for this MickeySoft mess. If I'm not wrong then the Server method is the best way for now. Hacking some files is an option but we all know it's only a matter of time till a false positive will popup. By the way what is Rufus using to bypass the requirements?
The last time I contributed to this thread (pointing out that OP was not the first to present the autounattend.xml solution here on MDL) my post got deleted but all of the above is now reinforcing my "original" point and @BAU's posts. but just to be empathetic @IXMas may have some knowledge, ... but he is obviously not conveying it properly to us (obviously less knowledgeable ) users
For the average user! Seeing all this my first wish was for the to simplify the whole process. There have been various attempts to finally make this simple, the simplest and transparent AutoUnattend.xml (great solutions are always simple). Solution with (AutoUnattend.xml) is for a new installation of Windows. I recommend to anyone who decides to permanently switch to the new Windows always a fresh installation, not an upgrade. System stability and many other things, save before private things, and reinstall the installed software on the new Windows, it requires logic itself. For testing itself, try to find another way, upgrading is not the happiest solution. For an upgrade, appraiserres.dll, so far I have no simpler solution than this one offered. You are offered to correct the file yourself or download an already edited one. Don't be afraid of various intimidations malice stems from jealousy, there is nothing dangerous here, but one thing is for sure, you do not endanger the stability of the future installed OS. If I come up with a better solution you will be notified. Have Fun! PS: A good horse raises a lot of dust.!!!
What's wrong with the Server method? I found that one the best because it's Antivirus prove. And if I'm not wrong, then it disables even more system requirements (Like TPM 1.2) then deleting the appraiserres.dll file.
It's wrong because he didn't come up with it, obviously.. That method doesn't help with CPU or RAM so it's not perfect. And yet here you are, doing literally the same thing just with a different file. Same s**t different day. There are no consequences. You have obviously never seen anything related to deployment before. All the installer does is apply install.wim to the disk, the rest is very basic servicing. You could replace it with the win7 installer and I'm pretty sure it'd still work. Are you saying that corporations and OEMs that use Windows Deployment Services have broken installs because they don't use the original installer? Do you think at all before you type? Just because you don't know how it works doesn't mean others don't It's an upgrade. From a build to a build. There is no need to reinstall. You've run out of ideas and are gonna pretend that that's now relevant? It's not a fully working clean install solution either because it doesn't work for unsupported CPUs and less than 4GB of RAM. And yet here you are, arguing that it's the best. Also, your Unattend will force the old installer, and as it has been said before, it will not work with upgrades at all. At least you finally wrote it yourself that your method is for clean installs only. Took you a while We have found simpler methods than you, because we know what we're doing. Your insistence on this half-assed approach is truly and completely backwards. Deleting the file is better and easier than modifying it, as anyone who knows what the installer does would tell you, and yet you still choose to pretend the installer files are copied from the boot.wim onto install.wim, which is complete bulls**t that I've shown you is not true. We're not "jealous", you haven't done anything that we could be jealous of. We're just baffled by your insistence on stupidity. It's just me repeating myself now, so try to respond to at least one argument I made. I'm pretty sure you can't but please do prove me wrong
My first and always present opinion is not to delete anything from Widows but to modify it as needed. Because it comes back to you negatively sooner or later. I know deleting the appraiserres.dll is not recommended, so I hold that it is wrong. Adjusting the option seems to be the least harmful form, which I do. That's it, those who don't like such an approach should keep digging through Windows at their leisure, leaving others, of different opinion, to be left alone. They have their own thread so let them convince whoever wants it there.
You don't delete it from Windows. You delete it from the installer. We've told you that countless times. So why don't you try to convince us your method isn't complete trash? Since when is whether something actually technically works "an opinion"?