Jump to content

Recommended Posts

Posted

Oh, btw, one more caveat, before I forget: could we have a list of "officially" redirectable folders and subfolder in windows (those with the location tab in the properties mask, so to speak) and possibly a way of making "officially unredirectable" folders redirectable (provide them with the location tab in the properties mask)? It is somewhwt frustrating, if I may, to find out about this "new" opportunity only after years of us going about in the realm of OS reduction. It is just awkward of us to resort to junctions to do what can be done naturally and/or (if possible) "naturalize the not-so-natural folders and subfolders" by a facility that the OS offers. The aim of the quest delves upon a remote wish of mine to keep just the "sheer Os core" (whatever contributes to and guarantees the booting to the desktop inferface, perhaps the windows system32 and syswow64 files) inside the vhd, and move the rest of files and/or folders outside the vhd, especially if we find that they can coexist and be shared with other corresponding ones in another os vhd (windows 10 and windows 11, for instance). thanks in advance for your possible contribution.   


Posted

Got this error when applying the image. What does it mean please?

Start applying WIM Image.
WIMHost cmdline: apply "S:\sources\install.wim" 1 W:\ -compact:lzx -wimlib -config:"Z:\WinNTSetup_v541_x64\Compact\WimBootCompress.ini"
WIMHost Return : 47
Error: Failed Applying Windows Image!
Setup aborted!

Thanks.

  • 2 weeks later...
Posted

Sure, just add a APPX dispaly name to the RemoveAPPX section.

Wildcards like ? and * are allow, too.

Posted

I figure u r talking about sample.ini, which already contains a list of apps u have surely added. is that all the lot there is to it or are there any more to possibly and safely remove?

Posted

@JFX

btw, sometimes I get a "could not copy the offline registry" message at the end of the minwinning procedure. Any idea how to troubleshoot it? if I try to reboot this specific vhd, it gets stuck at the first stage of the booting process saying it could not find system or system is corrupt; instead, if I copy the whole config dir to the windows\system32 subfolder before rebooting, everything goes spick and span, also the letter z:\ for ramdisk which, as I mentioned in earlier posts, was loaded as j:\ (the next useful drive letter) at other times.   

Posted

Don't know, you properly the first one ever getting this error message.

Make sure you not running out of free disk space. You need at least the size of \Windows\System32\config\SOFTWARE.

  • 2 weeks later...
Posted

Hello! The x86 version is flagged by MediaFire and blocked, idk if you can do anything about that :P

Posted
In the most recent Windows 11 builds, attempts to execute the
bypassnro command return the following error:
'oobe\bypassnro' is not recognized as an internal or external
command, operable program or batch file.
Fortunately, not all hope is lost. Enthusiasts quickly discovered
that it is still possible to restore the script. Here is how:
On the Windows 11 setup screen, press Shift + F10 and
type regedit and press Enter.
Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE
\Microsoft\Windows\CurrentVersion\OOBE.
Click Edit > New > DWORD (32-bit) and rename the new
value to BypassNRO.
Open the value and change its value data to 1.
Restart your system. You can now setup your computer
without an active internet connection or a Microsoft
Account.
Of course, OOBE\bypassnro is not the only way to skip some of
Windows 11's requirements. Still, it is one of the easiest and most
popular ones, so quite a lot of users will be upset about its demise.
Luckily, for now, it is possible to bring it back. There is just no info
on whether this method will last.
Source: @phantomofearth X

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...