Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Superfetch and Server 2012

Unanswered Superfetch and Server 2012

  • Sunday, September 09, 2012 5:59 PM
     
     
    Sign In to Vote
    1

    Hi,

    I am curious to know why Superfetch was implemented on Server 2012 and it's not working.

    We knew that on Server 2008 R2 it was present in kernel but not activated so with some homework we managed to get it going.

    It seems that on Server 2012 the whole service is incomplete.

    Files like sysmain.dll that has same hashcheck a the W8 x64 version are there, but then other files like readyboost.sys and various folder that go with it are missing. Also Superfetch service is not complete as a dependency is missing.

    All this can be fixed as you can import files and registry settings from W8, fix service dependency and also task schedule, this get's it to working but only for a while as then service stops on his own.

    My question is : will Superfetch service be fixed to work in a future Server 2012 update or will it remain there not working ?

    I do not find it logical to implement something that does not work.

    In anyway, any answer on the matter will appreciated.

    Thank you.

     

All Replies

  • Friday, September 14, 2012 2:22 PM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,

    Please make sure that the following services are started.

    l  File Information FS MiniFilter

    l  Remote Procedure Call (RPC)

    After that, please also check if the EnableSuperfetch and EnablePrefetcher under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters are enabled.

    The EnableSuperfetch key has the following values:

     0 = Disabled

     1 = Application start SuperFetching enabled

     2 = Boot SuperFetching enabled

     3 = Application start and boot SuperFetching enabled

    The EnablePrefetcher key has the following values:

     0 = Disabled

     1 = Application launch prefetching enabled

     2 = Boot prefetching enabled

     3 = Application launch and boot enabled

    Regards,

    Arthur Li

    TechNet Community Support

     
  • Friday, September 14, 2012 5:24 PM
     
     
    Sign In to Vote
    0

    Hi Arthur_Li,

    Thank you very much for your suggestion.

    I tested it out and it does not work and/or causes Server 2012 to crash on reboot with a BSOD -> “SYSTEM THREAD EXCEPTION NOT HANDLED".

    I also wish to point out something very important is that Superfetch works with Readyboost, I may be wrong but I don't think.

    Since Readybost files (readyboost.sys and so on) are not available in Server 2012, how can Superfetch possibly work ?

    As well as the registry entries you asked me to check, well there are not available in Server 2012, see below.

    Please do not misunderstand me or feel offended by my lines, but as I mentioned in my the 1st post, I did my "homework" and it appears that a non working service was implemented in Server 2012.

    I do not mind waiting till Microsoft fixes it or removes it with a Update, but I want to understand why not just make it work from the beginning or not implement it at like on R2.

    Nevertheless, I warmly appreciated your answer and concern about my post.

    Regards,

    Abafula

    It's a basic truth of the human condition that everybody lies. The only variable is about what.

     
  • Wednesday, September 26, 2012 9:26 AM
     
     
    Sign In to Vote
    1

    Really? No one at Microsoft knows why this service is installed on Server 2012 and doesn't function properly?

     
  • Wednesday, September 26, 2012 5:19 PM
     
     
    Sign In to Vote
    0

    Remember, this is a public forum - not a means of bringing incidents to Microsoft engineering's attention.  Though they do have some engineers that drop in from time to time, Microsoft has other channels for accepting questions/problem reports.

    You can always open a case with Microsoft support to have them help you find the issue in your particular environment.  If it is a bug in their software, Microsoft does not charge for the case.  If they spend time educating you, then they will charge you.

    tim

     
  • Wednesday, September 26, 2012 5:33 PM
     
     
    Sign In to Vote
    0

    Good evening Tim,

    I appreciate your answer as well as the solution you provided.

    Your answer would be justified if I was the only person having a issue with Superfetch on Server 2012 but I am not the only one.

    I would like to kindly ask you to install Server 2012 in a VM and please start Superfetch Service and let me know if it works.

    I do not pretend to be a Microsoft Engineer or a Talented Developer and I am sure I do not require "Education" either but I am able to recognize when a service is not running due to the fact that dependencies for that service are not resolved and files are missing.

    Once again, I insist on the fact that you must not misunderstand my lines and/or words I use, but I repeat again, WE (as some other people made some research too...) did our "homework" and the Superfetch DOES NOT WORK the way it's at the moment in Server 2012.

    Thanks anyway for taking a look at this topic.

    Regards,

    Abafula

    It's a basic truth of the human condition that everybody lies. The only variable is about what



    • Marked As Answer by Abafula Wednesday, September 26, 2012 5:36 PM
    • Unmarked As Answer by Abafula Wednesday, September 26, 2012 5:37 PM
    • Edited by Abafula Wednesday, September 26, 2012 8:08 PM
    •  
     
  • Thursday, September 27, 2012 10:54 AM
     
     
    Sign In to Vote
    1

    There are numerous posts to various Microsoft Developer, Partner, and Fansites that corroborate Abafula's remarks (as does my experience)... It is odd that this Windows Service even appears on Server 2012, no less that it's there and doesn't work as it's not even part and parcel of Server 2008 R2.

    The Microsoft's Server OS is not some casual toy product where this kind of undocumented build/issue can be expected to roll in the wild quietly; at the very least there's the additional 'attack surface' and what ever issue(s) that present that prevents this Service from running, or oversight that resulted in it being installed in the final release...

    It would be useful to understand Microsoft's motivations for including the Service at all, and why it doesn't work; is it for example some sort of compatibility place holder? I'm sure this eventually be addressed, sooner or later in some venue that doesn't incur additional support costs...


    • Edited by Hoak Thursday, September 27, 2012 10:55 AM
    •  
     
  • Monday, December 10, 2012 4:40 AM
     
     
    Sign In to Vote
    0
    Going on four months now, with numerous threads on this subject on various forums including MDL, MSFN, and W2S where no one has been able to get SuperFetch service working per Abafula's original post...  Again it is odd to see this service on the server product, but stranger still that it doesn't work -- was this just some half-assed compatibility fix, or is it intended that the SuperFetch service will be fixed and function at some point on Server 2012, or is there some as yet undocumented setting to get the service working properly? 
     
  • Saturday, February 23, 2013 9:36 AM
     
     
    Sign In to Vote
    0

    Hi,

    I didn't find a chance to give it a try but  has anyone configured the registry settings at:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Superfetch]

    here the full setting exported from a windows 8 pro virtual machine:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Superfetch]
    "ServiceFlags"=dword:00000400
    "LastReservedPriGenTime"=dword:0738897f
    "ProcessorTime"=dword:00000032
    "PfPdData"=hex:01,00,00,00,28,00,00,00,01,00,00,00,ee,87,ee,39,01,dc,fb,62,f0,\
      00,00,00,41,dc,20,b0,00,00,00,00,34,00,00,00,00,00,00,00
    "MemMonitorState"=hex(b):00,00,00,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Superfetch\DiskAssessment]
    "DiskNumber"=dword:00000000
    "RPM"=dword:00001068
    "SizeInGb"=dword:0000007f
    "PeakTransferMBsPerSecond"="  175.8099007894"
    "SeekBreakPages"=dword:000002ca
    "LongSeekMicrosecondsBase"="11821.4305164319"
    "LongSeekMicrosecondsPerSqrtGB"="    0.0000000000"
    "VolumeSerialNumber"=dword:68e9b492
    "VolumeCreateTime"=hex(b):6b,0c,cd,e7,a2,11,ce,01

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Superfetch\ReservedPriorityDbs]
    "0"="C:\\Windows\\System32\\systemsf.ebd"

     
  • Friday, May 03, 2013 10:14 PM
     
     
    Sign In to Vote
    0
    Going on four months now, with numerous threads on this subject on various forums including MDL, MSFN, and W2S where no one has been able to get SuperFetch service working per Abafula's original post...  Again it is odd to see this service on the server product, but stranger still that it doesn't work -- was this just some half-assed compatibility fix, or is it intended that the SuperFetch service will be fixed and function at some point on Server 2012, or is there some as yet undocumented setting to get the service working properly? 

    5 more months without any answer which solved the problem. Had some hope to get some fixes during this time. Nothing.