[antonbrk]

7guide.doc (attached). Here is a more verbose version of the guide I re-wrote for a family member. It is crafted for the "tech-nyet" (technically less sophisticated) user. Some steps are described with more detail and I've added related additional instructions that non-technical users might need, such as how to make a usb drive bootable, and how to modify a BIOS boot menu to install W7 from it. The attachment is a 117 Kb Word file (.doc). I've also placed a copy of it here, and an .rtf copy here . Please post here any discovered errors/typos in the file and I'll amend it and re-upload it. Much thanks to Liquid0624 and Liquidzgurl for their amazing work on the presets and guides. As a certified tech-nyet user myself, I was thrilled when my first run of 7elite64 went flawlessly, and I got a fully working slim version of W7 64 onto my 8 GB netbook, with 1 GB to spare after installing all my other programs (with a big SDHC for my files). Thanks for making that possible.

Attached File(s)

•  7guide.doc (116.5K)
  Number of downloads: 158

[nofeet]

Hi can somebody help me i have been trying all day to get this to work i keep getting errors when doing the removal process.
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-RecDisc-SDP-Package Er
ror: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Microsoft-Windows-Security-SPP-Component-SKU-
HomePremium-Package~31bf3856ad364e35~x86~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Microsoft-Windows-Security-SPP-Component-SKU-
Professional-Package~31bf3856ad364e35~x86~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-Security-SPP-Component
-SKU-Ultimate-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-ServicingBaseline-Ulti
mate-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-Shell-HomeGroup-Packag
e Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-Shell-MultiplayerInbox
Games-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-SnippingTool-Package E
rror: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-StickyNotes-Package Er
ror: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Microsoft-Windows-StorageService-Package~31bf
3856ad364e35~x86~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-TerminalServices-Publi
shing-WMIProvider-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-TerminalServices-Remot
eApplications-Client-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-VirtualPC-Licensing-Pa
ckage Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-VirtualPC-USB-RPM-Pack
age Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-VirtualXP-Licensing-Pa
ckage Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-WinOcr-Package Error:
0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-WindowsMediaPlayer-Tro
ubleshooters-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Microsoft-Windows-Xps-Foundation-Client-
Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Networking-MPSSVC-Rules-HomePremiumEdition-Pa
ckage~31bf3856ad364e35~x86~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Networking-MPSSVC-Rules-BusinessEdition-Packa
ge~31bf3856ad364e35~x86~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - An error occurred - Networking-MPSSVC-Rules-UltimateEdition-
Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I am using Windows Ultimate 32bit OEM.

[Junior2613]

did you run the wim tweak first ??

[nofeet]

Junior2613, on Jan 13 2010, 04:20 PM, said:

did you run the wim tweak first ??

So you mount then do the wim tweak then the removal?

I'll give it a go then. Thanks

[nofeet]

I tried mounting, then the tweak then the removal.bat but no luck. Getting different errors.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 2

An error occurred while attempting to access the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

[sequoia464]

Step 7 of the guide - "image" values given are for Ultimate or Home premium. My guess is that professional will use the same value as Ultimate (4), can anyone confirm this? - Thanks

[Eikcuhc]

Hey guys, new to the forum.

I am using 7elite32 for my Windows 7 32-bit Professional (Changed the numbers in mount and removal to "4") and have gotten to the step where you need to run "cleanup" however whenever I do I get

C:\7elite32\batch>cleanup
The system cannot find the file specified.

The operation completed successfully

The operation completed successfully

The operation completed successfully
The system cannot find the file specified

anyone know what could be causing this?

[nd4spdbh]

Hey guys i just finished me 7 elite slimming and went to install it on my netbook with a 4gb ssd (3.5 really) Now i know it will take less than this so how do you make it to where it doesnt care how big the disk is cus right now it wont let me install it on a drive so small.

I thought it might be taking into account the size of the page file so i swapped out my 2gb stick with the original 512mb stick and the disk size required 3954MB didnt change... so im at a loss.

This post has been edited by nd4spdbh: 25 January 2010 - 06:36 PM

[runLoganrun]

So, a while back, idk 2-3 mos, I tried the 7media64 batch files, and process for component removal.
Everything went fine, until, and don't hate me here, but I did get an error, such that I could not continue using it, don't remember what it was now, but had to do with IP address (I was trying to connect to my server).
But, that's not the point here so not so important, however if someone did get a similar error please elaborate any fixes you employed.
To the point- Sorry, but not sure I get this exercise, I mean I get it, the point, but I can take a win7 ult x64 .iso, and using vLite only to remove components, easily get a 1.9GB install file that works perfectly. What is the advantage to all the other processes, speed, yes I know, but the install file is not that much smaller, if at all, and then there is potential for all these errors that I've read about in the thread, along with the one that I got. One thing that I dread, and this has happened with vLite for me, esp. before I figured out what you couldn't do with 7 and vLite, is getting the majority of my apps installed, and configuring everything the way I like it, restoring databases, and so on, only to find that my installation is hosed, so then it's back to the drawing board, and reinstalling everything again, and this is time consuming, and I've other things that need to be done too. I suppose I should acquaint myself better with virtualization, but in order to get an accurate demo, you need to load everything anyway, so cloning my OS drive prior to new install, and doing actual full install seems to be the only way to get accurate test of functionality, then can just re-clone, and I'm back in business.
Back to the question, and apologies if I'm being completely ig'nant here but how much better is the final install, than just removing the components with vLite?? I want to make another go at it, but don't want to spend days fixing errors, or reinstalling again, know what I mean?
But, props to the authors of this guide and accompanying batch and .ini files, very impressive, no disrespect at all, just trying to get a better feel for it.
Thanks very much,
RLR

[nd4spdbh]

nd4spdbh, on Jan 25 2010, 04:35 PM, said:

Hey guys i just finished me 7 elite slimming and went to install it on my netbook with a 4gb ssd (3.5 really) Now i know it will take less than this so how do you make it to where it doesnt care how big the disk is cus right now it wont let me install it on a drive so small.

I thought it might be taking into account the size of the page file so i swapped out my 2gb stick with the original 512mb stick and the disk size required 3954MB didnt change... so im at a loss.

Any answers?

[z3phir]

for windows professional x64 the value is 3 ?

[Kelsenellenelvian]

z3phir, on Jan 31 2010, 01:23 AM, said:

for windows professional x64 the value is 3 ?

There is no value for windows XP professional...

[z3phir]

who said xp professional ? i said windows professional x64 (Windows 7 Professional 64 bit) this is a thread about windows 7 i'm not a moron for xp i use nlite

[z3phir]

i tried to use 7media64

my windows is 7 professional x64 the image i use is a original msdn

i changed the value to 3 in mount.bat and removal.bat because i want windows 7 professional x64

mounted ok but at remove i get some errors

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Microsoft-Windows-Security-SPP-Component-SKU-
HomePremium-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log



Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Networking-MPSSVC-Rules-HomePremiumEdition-Pa
ckage~31bf3856ad364e35~amd64~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

any idea what is wrong ?

[nd4spdbh]

So is there anyway i can install win 7 on something smaller than 3954mb..

also ANOTHER QUESTIONS

what package is it that removes the built in zip folder extractor?

[theKramer]

z3phir, on Jan 31 2010, 10:24 AM, said:

An error occurred trying to open - Microsoft-Windows-Security-SPP-Component-SKU-
HomePremium-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log



Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

An error occurred trying to open - Networking-MPSSVC-Rules-HomePremiumEdition-Pa
ckage~31bf3856ad364e35~amd64~~6.1.7600.16385 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log[/code]

any idea what is wrong ?

I think it might have something to do with the fact that those are Windows Home premium packages. Check to see if there are any other WHP related packages in the list of packages to be removed. If there arent, then its it must be something to do with that.

I would just delete the lines from the batch file.

[srbliss]

I am having a heck of a time with the 7extreme64 batch files. I have followed the instructions to a T and everything seems correct. When I run the 'mount' command in the command prompt I get the following errors.

C:\7extrem64\batch>mount
The system cannot find the path specified.
The system cannot find the path specified.

C:\7extreme64\batch>


Any ideas? I have the ImageX.exe in the C:\7extreme64\wtools folder and the source files are in the C:\7extreme64\source folder. My OS is XP64 that has been heavily Nlited. I got the same errors on a W7-64 install (full install of the DVD.)

Steve

Edit - fixed it. When I extracted the files I made a typo note the extra E above.

This post has been edited by srbliss: 03 February 2010 - 04:23 PM

[neuropass]

At the cleanup step i keep getting error.. what should i do?

[neuropass]

Eikcuhc, on Jan 21 2010, 10:40 AM, said:

Hey guys, new to the forum.

I am using 7elite32 for my Windows 7 32-bit Professional (Changed the numbers in mount and removal to "4") and have gotten to the step where you need to run "cleanup" however whenever I do I get

C:\7elite32\batch>cleanup
The system cannot find the file specified.

The operation completed successfully

The operation completed successfully

The operation completed successfully
The system cannot find the file specified

anyone know what could be causing this?

same here...

ANY help here guys? is this topic still alive??

This post has been edited by neuropass: 03 February 2010 - 12:25 AM

[neoby]

Hello everyone,

I just found this excellent topic, willing to lighten my HTPC. But, to me, all the links to batch archives appear to be dead (links to docs work just fine from media fire). Could someone repost/send me the archives ? (The one I am planning to use is 7media32).

Thank you in advance

Ps: I am a bit surprised that other posts from today are not mentioning this problem !

*please excuse my english-level*