unless I have an explodeedoh these are En-US checksums Code: 213a8a0f8849516704101cb6c49f6a027b0d6d5f *en_office_professional_plus_2016_x86_x64_dvd_6962141.iso 6d8936721f6282c3ae08f39b7886c91a141b7552 *SW_DVD5_Office_2016_64Bit_English_MLF_X20-42479.ISO b7d9ba9e6b975b7f1a574a7bef4e323c2b816da1 *SW_DVD5_Office_2016_W32_English_MLF_X20-41370.ISO cfbdbf902f26a78f68bb5f91a37e6cdac2252429 *SW_DVD5_Office_Professional_Plus_2016_64Bit_English_MLF_X20-42432.ISO dc0c0dce5c6695a6248eccc1e1a44bb066e01280 *SW_DVD5_Office_Professional_Plus_2016_W32_English_MLF_X20-41353.ISO 84ec3befa0c8229610b6f790188b2610e875760f *SW_DVD5_Project_2016_64Bit_English_MLF_X20-42644.ISO 4c4f88c331a517164292bbf10f2c60d8354c4b5b *SW_DVD5_Project_2016_W32_English_MLF_X20-41488.ISO 9a83079bca618a308841caec416fd2f476959af1 *SW_DVD5_Project_Pro_2016_64Bit_English_MLF_X20-42683.ISO 0452fe6fee407d73cfb677fcd4ae962560c2ce93 *SW_DVD5_Project_Pro_2016_W32_English_MLF_X20-41516.ISO d44808089415cd8883a0e2b2570e10c1c992ee1a *SW_DVD5_Visio_Pro_2016_64Bit_English_MLF_X20-42764.ISO 28b0518210f1942eb57aa6ddc6eeabebc548558a *SW_DVD5_Visio_Pro_2016_W32_English_MLF_X20-41585.ISO fb646fde23ef69c195fa01913630721458a221db *SW_DVD5_Visio_Std_2016_64Bit_English_MLF_X20-42792.ISO d1f24b3e56f182fe30b656d830f0485c272a2f91 *SW_DVD5_Visio_Std_2016_W32_English_MLF_X20-41613.ISO Code: 1ec61a04db9fc9697dc9490679171f46d936e6d3 *SW_DVD5_Access_2016_64Bit_English_MLF_X20-42273.ISO 796ff7f1b46bde5422ac6337d9bad2eef9bd21ea *SW_DVD5_Access_2016_W32_English_MLF_X20-41171.ISO 4ef5c678a0b2527f056ca8b0ed0d56f9a68bfb66 *SW_DVD5_Excel_2016_64Bit_English_MLF_X20-42312.ISO 66147cbbc7e06082838f1fe3a629fa362b12366e *SW_DVD5_Excel_2016_W32_English_MLF_X20-41210.ISO 2b2d5cb0e5f30b14471d725d4bc63fab2c4bd43d *SW_DVD5_Outlook_2016_64Bit_English_MLF_X20-42535.ISO 6f0d63e8e8b4d33903d19e4ccbda464464283d53 *SW_DVD5_Outlook_2016_W32_English_MLF_X20-41410.ISO d0193139a078ee8916258bba20acfa2af41bb929 *SW_DVD5_PowerPoint_2016_64Bit_English_MLF_X20-42592.ISO 7ba5befc42daee92bb4deff43fe5eb524813c6bb *SW_DVD5_PowerPoint_2016_W32_English_MLF_X20-41450.ISO e4829624e6584d29701a22a75a6753f7a423c16d *SW_DVD5_Publisher_2016_64Bit_English_MLF_X20-42723.ISO 9263eccc8e5ee670408d3bffa4028f18d508cde4 *SW_DVD5_Publisher_2016_W32_English_MLF_X20-41547.ISO a70a664c0efc2aacda84eb980cba56b75d21eba3 *SW_DVD5_Skype_for_Business_2016_64Bit_English_MLF_X20-42352.ISO a829862ffda2212ba8c68dccfb543781485166af *SW_DVD5_Skype_for_Business_2016_W32_English_MLF_X20-41250.ISO 516426677456ae65534a361a63bd5b473fe06231 *SW_DVD5_Word_2016_64Bit_English_MLF_X20-42822.ISO 4c6fb3f3a507613b58e76e6cfa249ee8c165f56e *SW_DVD5_Word_2016_W32_English_MLF_X20-41643.ISO Code: a9d31cef8aef85e5d0adaec49628c33bc59181a2 *SW_DVD9_Office_Multi_Lang_Pack_2016_64Bit_MultiLang_Disk_1_MLF_X20-42855.ISO a6e7df8af81a823a5b6873870268f80236c86cce *SW_DVD9_Office_Multi_Lang_Pack_2016_64Bit_MultiLang_Disk_2_MLF_X20-42856.ISO 72ff62328bf599d1754bdc4f422b943395e1b16a *SW_DVD9_Office_Multi_Lang_Pack_2016_W32_MultiLang_Disk_1_MLF_X20-42853.ISO f90bc973ff4ab94f9f351114547cd68a505e7161 *SW_DVD9_Office_Multi_Lang_Pack_2016_W32_MultiLang_Disk_2_MLF_X20-42854.ISO 6dcea9b9c3ba7acd507efe7633d6a4759209aedf *SW_DVD5_Proofing_Tools_2016_W32_MultiLang_ComplKit_MLF_X20-42860.ISO ceab52a5ccf32322a4ea05c5cf8954d7e0d307f9 *SW_DVD5_Proofing_Tools_2016_64Bit_MultiLang_ComplKit_MLF_X20-42861.ISO ca4e8e21cdfff259e1b977264738a217d63c0c92 *SW_DVD5_Office_Multi_Lang_Pack_2016_64Bit_English_MLF_X20-42392.ISO bc87f2ad86b0824fa6f1dcb6d77787ee61add10a *SW_DVD5_Office_Multi_Lang_Pack_2016_W32_English_MLF_X20-41290.ISO df4d28db41da3ed4c659a69a3f300305dac74111 *SW_DVD5_Office_Pro_2016_32-BIT_X64_MultiLang_LIP_Comp_Kit_MLF_X20-42858.ISO
The checksum that you and I have match, but the checksum I get when I run SW_DVD5_Visio_Pro_2016_64Bit_English_MLF_X20-42764.ISO, from the first page of this thread, is an SHA-1 of AF0CAE1BA81EC994724992FB855FD23D0C3775C8. Again, the file works directly from the magnet on page 321.
Hello, should I install x64 or x32 version of office 2016? I think I remember reading somewhere about some reasons as to why one should install 32-bit version of earlier office (2010 or 2013)
there is no real reason to install x64 (unless you work with files bigger than afaik 2G (4G?) ) i prefer x32 for compatibility reason. x64 is not faster coz non spatial x64 processor features used x64 only use 64 bit pointer (pure waste storage - x86 use 32bit pointer for the same ) EDIT: 2PC with same Hardware: os: x64 + x64 progs -> fast os: x64 + x86 progs -> more quickly os: x86 + x86 progs -> fastest only special gamer and some rare video editors (commercial) make use of x64 processor features x64 is faster, is a fairy tale
Yeah, thanks, I googled to remind myself, x64 doesn't support older add-ons, ActiveX, Access DBs compiled for 32-bit etc. So I guess we'll be running 32-bit office forever What should I use wof Win10 & Office, KMS (MTK), KMSpico, or smth else? I don't know the difference between these different solutions. Thanks.
Hi!!! What KMS Tool is better for activate Office 2016 Pro Plus, Project and Visio VL on Windows 10??? Can I update the Office like Windows activated via KMS tool???? Does anyone logged in with Microsoft account in an Office activated via KMS Tool???
You should choose Microsoft Toolkit. Link is in my signature. Before downloading read the first post of thread and try. All the best
The tools you wrote are all KMS solutions. No differences between them. You should go for MTK for smooth activation.
How about proofing tools for the MSI version? I can only find ones for C2R, are those for MSI only available through VLSC? If so, can someone get his hands on Dutch Belgium x64?