Group: Forum Members
Well if your previous Rescue Media builds that you previously confirmed worked -- on this specific PC? -- are no longer working, then it sounds like something else has changed on your PC somehow whether somebody did it deliberately on that system or something else caused the change.
For the rest, I can't say I recall the last time I spent this much time writing multiple posts across two different forums trying to convince one person to do something so simple and benign. So I'm going to try one last time, but then I'm just going to leave it to you to try it or not.
No, blowing away the Rescue Media cache does not blow way the WinPE files that Reflect uses to generate Rescue Media. If that would have happened, I would have told you -- as you've seen, I'm not shy about writing long posts. Anyhow, you're only blowing away the cache of built Rescue Media files, including the WIM that contains all of the Rescue Media customizations, as well as any drivers in the Drivers folder. The "base" WinPE file cache, including its entirely distinct WIM file, is stored elsewhere. And with WinRE, Reflect doesn't cache files anyway because it draws them from the Windows Recovery file set that already exists on your PC, not anything it downloaded. But if you're curious, even if you DID go out of your way to also blow away the WinPE cache files (buried under Reflect's folder under C:\ProgramData), then the next time you tried to build Rescue Media on a WinPE version that Reflect no longer had cached files for, it would prompt you to download them. You would not have to "force" anything. Again MPSPAN: if you didn't have to force anything to build Rescue Media before this point, then doing this won't require you to force anything to build it afterward either. Similarly, any drivers that Rescue Media Builder automatically copied to the Drivers folder would automatically be copied again. If you happened to copy any other drivers into that folder manually, then yes you'd have to do that again, just like you did originally. Or you could just grab those manually copied drivers out of the C:\boot folder that you'll be renaming. Picking drivers out of a FileRepository folder only applies for any drivers you want to force Reflect to incorporate into Rescue Media. If you don't even know of a driver you want to force Rescue Media Builder to copy, then that discussion is moot.
I really don't understand why you seem so concerned that you'll have to "force" a bunch of things to happen just to get Rescue Media working after you do this -- particularly when you'll be keeping the current C:\boot folder by simply renaming it anyway! If something doesn't go well, then just delete the new C:\boot folder that Rescue Media Builder will create and rename your previously renamed folder back to "Boot", and you're back to where you are now! But the reality is that if Rescue Media Builder sees that some needed content is missing, it will either recreate it or prompt you to redownload it. Everything in the C:\boot folder falls into the former category -- as I already explicitly told you. If you take my word for it, then just rename the folder already, knowing you can rename it back. If you DON’T take my word for it and don't believe that renaming a folder back will be enough to recover, then I doubt reading any more posts of mine will change anything, in which case there's no point in my continuing with you.
And from a purely pragmatic standpoint, it's odd to me that you're putting this level of caution and worry around a process to reset your Rescue Media file set given that a) you're not actually deleting anything here, and b) your current Rescue Media builds don't work in the first place!! So what exactly are you so worried about losing here? Absolute worst case, suppose you can't build Rescue Media after this rename operation and somehow you can't rename your folder back, although I don't see how either of those would actually happen. Even then, given that you can't build working Rescue Media right now, the inability to build Rescue Media at all doesn't seem any worse from a practical standpoint. And given that there will also still be people on forums to help with any problems you actually DO encounter, once again I don't see why you're fretting about this so much beforehand and asking about so many things you THINK you might encounter.