Windows File Protection problem on OEM setup.


Go Back   Computer Help Articles > Windows XP Setup Deployment
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-05-2006, 06:22 AM
Ian
 
Posts: n/a
Default Windows File Protection problem on OEM setup.

Recently bought-in a batch of budget machines with OEM XP Home because
management don't want to spend too much on this project. Unfortunately they
came with Norton and other foistware, so rather than trying to remove this
junk I formatted and used the I386 folder to do a clean reinstall.

Reinstall and activation went OK but every time new software is installed,
we get a complaint from Windows File Portection (SFC) that system-files are
the wrong versions, and it demands the Windows CD (Which never existed
anyway!) Strange thing is that it demands an XP PROFESSIONAL CD, though this
is definitely XP Home.

In fact, It won't accept any XP CD as a suitable source, or the original
I386 contents.

This is obviously due to some kind of adulteration that OEM has done to the
original install-files, perhaps they customised them using XP Pro files by
mistake.

With hindsight (wonderful thing!) I should've used a kosher OEM XP Home disc
instead.

Anyway, question is, how might we stop this? I could hack SFC to disable it
altogether, but a proper fix would be bettter.


Reply With Quote
  #2  
Old 01-05-2006, 06:22 AM
Carey Frisch [MVP]
 
Posts: n/a
Default Re: Windows File Protection problem on OEM setup.

You may be prompted to insert a Windows XP Professional CD
when you run the System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/kb/897128/en-us

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

-------------------------------------------------------------------------------------------

"Ian" wrote:

| Recently bought-in a batch of budget machines with OEM XP Home because
| management don't want to spend too much on this project. Unfortunately they
| came with Norton and other foistware, so rather than trying to remove this
| junk I formatted and used the I386 folder to do a clean reinstall.
|
| Reinstall and activation went OK but every time new software is installed,
| we get a complaint from Windows File Portection (SFC) that system-files are
| the wrong versions, and it demands the Windows CD (Which never existed
| anyway!) Strange thing is that it demands an XP PROFESSIONAL CD, though this
| is definitely XP Home.
|
| In fact, It won't accept any XP CD as a suitable source, or the original
| I386 contents.
|
| This is obviously due to some kind of adulteration that OEM has done to the
| original install-files, perhaps they customised them using XP Pro files by
| mistake.
|
| With hindsight (wonderful thing!) I should've used a kosher OEM XP Home disc
| instead.
|
| Anyway, question is, how might we stop this? I could hack SFC to disable it
| altogether, but a proper fix would be bettter.

Reply With Quote
  #3  
Old 01-05-2006, 06:22 AM
Ian
 
Posts: n/a
Default Re: Windows File Protection problem on OEM setup.

That looks very likely, I'll check it out next time I'm onsite.

Thanks, and have a good festive season.


Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Update installation fails Harold Cataquet Windows Update 23 01-05-2006 05:17 PM
0x80070002 - DataStore GONE?! jmac30 Windows Update 3 01-05-2006 05:12 PM
Troubleshoot update failure DLS Windows Update 1 01-05-2006 05:03 PM
One-way connection: networked XP/2000 PC's Cheryl Windows XP Network Web 22 01-05-2006 04:11 AM
USB Mass Storage Device - This device cannot start. (Code 10) lobo201 Windows XP Hardware 11 01-05-2006 02:15 AM


All times are GMT. The time now is 06:51 AM.


Powered by vBulletin Version 3.5.2
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd. SEO by vBSEO 2.3.2 © 2005, Crawlability, Inc.

Windows File Protection problem on OEM setup.