![]() ![]() A couple of hours work at most and you will find what is making ntlite not recognise your edition anymore. Run dism to remove 1 package group at a time then restart, start ntlite in live mode, if ntlite doesnt complain, move on to the next package, then repeat restart, start ntlite in live mode, if ntlite doesnt complain, move on to the next package and so on. ![]() Copy ntlite over to the test partition Program Files folder. Create a test partition on your machine that has ntlite installed, 40gb should be enough. cab file so if it breaks something you can quickly reinstall it. By default most w7 packages are hidden from dism.įw6, package removals on a live install can be a quick way of finding what removal can break what, but you need to export X package 1st to a. Some apps you dont remove because theyre. ![]() You can easily remove all default apps with them. Without knowing what packages removed it is difficult to spot the bogey but it is probably something Edition specific and or Licensing and or Client Related. NTLite Home/Pro/Business licenses have the same feature set. The only time/s i have seen this warning is doing a super barebone w7 then reloading it. You are quoting best practice procedure but although we "Lite" here dism removals are popular prior to "liting" so lets try to sort fw6 out inhouse, too many websites get snotty if you dont do things their way with that "our way or the highway" attitude. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |