Oct 02, 2017 2010 Full Download. This site has direct download links to Digital River for most Office 2010 installation file, Office bundles and standalone programs. You may have to scroll down to find your language. Office 2013 Professional Plus / Office 2013 Language Pack / Project 2013 Professional / Visio 2013 Professional.
Look in the Disabled Items list for Acrobat PDFMaker Office COM Add-in. If Acrobat PDFMaker Office COM Add-in is in the list, then select it, click Enable, and click Close.
Then close and reopen the Office application. If Acrobat PDFMaker Office COM Add-in is not in the list, then use Windows Explorer to look for PDFMOfficeAddin.dll in C:Program FilesAdobeAcrobat DC, 2015, or 2017PDFMakerOffice. If the file is not present, then go to Solution 5 for instructions on how to repair your Acrobat installation.Note: If you installed Acrobat to a location other than the default of C:Program FilesAdobe, then modify the folder path above for your installation location. In the Command Prompt window, type regsvr32 followed by a space and the path that you noted in Step 1.
Enclose the path in quotation marks. For example, if PDFMOfficeAddin.dll is in its default location, then you would type the following command:For Acrobat DC: regsvr32 'C:Program FilesAdobeAcrobat DCPDFMakerOfficePDFMOfficeAddin.dll'For Acrobat DC Classic (2015): regsvr32 'C:Program FilesAdobeAcrobat 2015PDFMakerOfficePDFMOfficeAddin.dll'For Acrobat 2017: regsvr32 'C:Program FilesAdobeAcrobat 2017PDFMakerOfficePDFMOfficeAddin.dll'. Look for Acrobat PDFMaker Office COM Add-in in the list. If Acrobat PDFMaker Office COM Add-in appears in the list but the check box beside it is not selected, then click the check box.
Then close and reopen the Office application. (If you can't place a check mark, and if you have already tried Solution 1, then select Acrobat PDFMaker Office COM Add-in. Click Remove, and proceed to the next paragraph.).
If Adobe PDFMaker COM Add-in is not in the list of available add-ins, then click Add and navigate to C:Program FilesAdobeAcrobat DC, 2015, or 2017PDFMakerOffice. Select PDFMOfficeAddin.dll. Then close and reopen the Office application.Note: If you installed Acrobat to a location other than the default of C:Program FilesAdobe, then modify the folder path above for your installation location.
Just an odd interesting one.On a clean load of the fall creator's update, or an update from the Spring to Fall creators update to the fall creators update I'm experiencing the following issue with Office 2010 Standard 32 BitI can create a file and save it, however making any modifications to the file and hitting save again prompts me with errors upon saving - usually file permission error, however once KES10SP2 is uninstalled everything works again.I've verified this on Documents/Excel Spreadsheets/Outlook Signature modificationsAll Microsoft Updates & KES Updates as of are installed. Hello.Please clarify whether only uninstalling KES resolves the issue. Does simply exiting KES or disabling all components (or, specifically, some particular component) resolve it as well? Please collect KES traces while all other components are off, and the issue is reproduced. Also, please provide a GSI report from the host.Unfortunately, before the release of KES 11, its behavior can only be investigated as part of the beta-testing.Thank you.Uninstalling does solve the issue with being able to write Microsoft 2010 filesDoing a Pause system protection & control does not solve the problem- Traces included, currently re-running the GSI & attempting to get it below 4MB in size. Hello.Please clarify whether only uninstalling KES resolves the issue. Does simply exiting KES or disabling all components (or, specifically, some particular component) resolve it as well?
Please collect KES traces while all other components are off, and the issue is reproduced. Also, please provide a GSI report from the host.Unfortunately, before the release of KES 11, its behavior can only be investigated as part of the beta-testing.Thank you.My GSI is about 4.6MB in size.
Down to about 4.4MB in size using 7zip 16's ultra compression, is there a method for getting it up to you as is, or should I re-run it without windows logs to see if that reduces 'about 5MB in total pre compression' the size enough to upload here? My GSI is about 4.6MB in size. Down to about 4.4MB in size using 7zip 16's ultra compression, is there a method for getting it up to you as is, or should I re-run it without windows logs to see if that reduces 'about 5MB in total pre compression' the size enough to upload here?Please clarify whether all components in KES were disabled at the time traces were collected. If possible, please do 'Pause protection and control' and collect a set of traces together with a log. This will allow to see which processes actually modify permissions and how.GSI report can be uploaded to any resource, and a link provided here.Thank you for reporting. We will investigate based on information provided by Pyro411, and post about the progress in this topic.Thank you.
Please clarify whether all components in KES were disabled at the time traces were collected. If possible, please do 'Pause protection and control' and collect a set of traces together with a log. This will allow to see which processes actually modify permissions and how.GSI report can be uploaded to any resource, and a link provided here.Thank you for reporting. We will investigate based on information provided by Pyro411, and post about the progress in this topic.Thank you.GSI can be found here;Procmon PML file can be found here - warning it's about 850MB when decompressedNew trace logs attached - All Endpoint controls and protections disabled via pause protection and control during gathering of traces & procmon. Hello!Could you please check if the disabling the driver klvfs would solve the issue?Please also install the patch pf3099. You can get it in the incident via companyaccount.kaspersky.comThanks!Good morning;Sadly I'm not seeing an incident for this in my company account & created a new company account connected to the email that's identical to the one on the forum, I did submit a request to get it though via the ticket system in the company account portal.Sorry silly question, what's the best method to disable the klvfs driver?
Hello,please give us the ticket number.Did you try to rename the driver and reboot the machine?Thank you.Good morning;Sorry for the delay, the ticket number for when I got the file is INC20After renaming klvfs.sys and rebooting I'm able to modify files via office againI did also try loading PF3099 after renaming klvfs.sys as a test, however upon boot it was stuck at the login screen with all forms of input that I tested were disabled 'Keyboard/mouse/Incoming RDP sessions' however the clock continued on properly so it wasn't a hard system lock. This required a system restore to regain functionality. Good morning;Sorry for the delay, the ticket number for when I got the file is INC20After renaming klvfs.sys and rebooting I'm able to modify files via office againI did also try loading PF3099 after renaming klvfs.sys as a test, however upon boot it was stuck at the login screen with all forms of input that I tested were disabled 'Keyboard/mouse/Incoming RDP sessions' however the clock continued on properly so it wasn't a hard system lock. This required a system restore to regain functionality.The patch is not known to cause such issues; furthermore, it potentially fixes the described issue. If possible, please check if this behavior is reproduceable, or if another test host can be used. If reproduced, please describe the exact actions that lead to this.
Did you rename the driver back before installing the patch? What happens if you disable Device Control (via policy, or after excluding this host from the group that enforces a policy) before installing the patch?Thank you. The patch is not known to cause such issues; furthermore, it potentially fixes the described issue. If possible, please check if this behavior is reproduceable, or if another test host can be used. If reproduced, please describe the exact actions that lead to this.
Did you rename the driver back before installing the patch?