Hulkster
New member
Dear people of Sysnative,
First I would like to introduce myself, since I am new on this forum. I am Hulkster (Ferry) and I live in The Netherlands and PC's (hardware and software) have been a hobby and occupation for almost 20 years. My dear friend Tom recommended that I should come over (from another forum that doesn't have a great reputation). He told me this 2 years ago, but since then our paths separated and I wasn't in any immediate trouble (pc wise) and was struggling with my health. Now I am back and willing! :lol:
Concerning the problem I have, it all started with a newly installed Windows 7 (Ultimate) on a separate PC (in my bedroom). I updated it pretty quickly with a method I found here: 2 easy steps to speed up Windows 7 Update scans | InfoWorld and after I updated it I wanted to install Microsoft Office 2003. I still find version 2003 the best (in case you might be wondering why I would install it) and while i was doing so, I got the error (in my application logs and on screen) "Error 1719. The Windows Installer Service Could Not Be Accessed". The installation stopped then! So I searched for this error and found (among others) this page: Fix Windows Installer Error 1719 - Instant-Registry-Fixes.org. I tried that but that didn't work, so then I found somewhere that you had to run SFC and that it could fix this problem. I found it a bit strange because it is a very new installation, but then again I know anything can happen (even with fresh installations). And so I run SFC /scannow and it could not fix all my problems it said.
I use a tool to run sfc /scannow, which can be found here: SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files That is also the forum I was talking about and the people that are very rude. I like this tool because you don't have to type the commands (not because I am lazy) and it also copies the logfile that it creates directly to your desktop! I included the logfile that SFC created in this post! Oh and I also run System Readiness Tool (V34 October 2014), but it said there where no errors.
My problem isn't a problem that has to be solved immediately, so there is no rush, but I would like to get it fixed in time. Tom told me "we have a great team and you’ll be in very good hands" and I know Tom is a honest, sincere, genuine, hard working person and so I believed him right away!:thumbsup2: If someone could tell me why my SFC can't make some errors, then I would be very grateful!
1
With kind regards,
Hulkster
First I would like to introduce myself, since I am new on this forum. I am Hulkster (Ferry) and I live in The Netherlands and PC's (hardware and software) have been a hobby and occupation for almost 20 years. My dear friend Tom recommended that I should come over (from another forum that doesn't have a great reputation). He told me this 2 years ago, but since then our paths separated and I wasn't in any immediate trouble (pc wise) and was struggling with my health. Now I am back and willing! :lol:
Concerning the problem I have, it all started with a newly installed Windows 7 (Ultimate) on a separate PC (in my bedroom). I updated it pretty quickly with a method I found here: 2 easy steps to speed up Windows 7 Update scans | InfoWorld and after I updated it I wanted to install Microsoft Office 2003. I still find version 2003 the best (in case you might be wondering why I would install it) and while i was doing so, I got the error (in my application logs and on screen) "Error 1719. The Windows Installer Service Could Not Be Accessed". The installation stopped then! So I searched for this error and found (among others) this page: Fix Windows Installer Error 1719 - Instant-Registry-Fixes.org. I tried that but that didn't work, so then I found somewhere that you had to run SFC and that it could fix this problem. I found it a bit strange because it is a very new installation, but then again I know anything can happen (even with fresh installations). And so I run SFC /scannow and it could not fix all my problems it said.
I use a tool to run sfc /scannow, which can be found here: SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files That is also the forum I was talking about and the people that are very rude. I like this tool because you don't have to type the commands (not because I am lazy) and it also copies the logfile that it creates directly to your desktop! I included the logfile that SFC created in this post! Oh and I also run System Readiness Tool (V34 October 2014), but it said there where no errors.
My problem isn't a problem that has to be solved immediately, so there is no rush, but I would like to get it fixed in time. Tom told me "we have a great team and you’ll be in very good hands" and I know Tom is a honest, sincere, genuine, hard working person and so I believed him right away!:thumbsup2: If someone could tell me why my SFC can't make some errors, then I would be very grateful!
1With kind regards,
Hulkster
